[ https://issues.jboss.org/browse/JBIDE-23131?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-23131: --------------------------------------- Stuff to take into account: - integration tests are much more complicated, on its own run ~2 hours full suite (1-1,5 Smoke suite) on CDK instance. On remote instance it would be much longer and if user does not use nested desktop environment, user could get blocked for the period. Thus there should be a specific profile which would trigger integration tests (it should not be run by default with mvn clean verify, also tests requires many arguments for execution, like server credentials, could be some default settings somewhere and have a proper documentation for it) - integration tests uses stuff from pluginCustomization, it should be copied too. Also common stuff from parent poms in integration tests repo - QE should have push rights too - differentiate between unit tests and integration tests (integration tests run with different runner, should not run together, more like integration tests could follow unit tests in whole work flow to avoid running like Unit - Integration - Unit - Unit - Integration - Unit etc.) - PRs to integration tests should always have QE ack -- This message was sent by Atlassian JIRA (v6.4.11#64026)