[jbosstools-issues] [JBoss JIRA] (JBIDE-24547) Refactor ITests settings in parent pom

[Pavol Srna (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-24547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13422379#comment-13422379 ] 

Pavol Srna commented on JBIDE-24547:
------------------------------------

I investigated and found out that we cannot use maven lifecycle to have separate settings for unit tests, UI tests and itests. All are run by tycho surefire and in the same 'integration-test' phase. So I'm coming with 2 other options:

1) run itests by default. Disadvantage is that we need copy/paste itests settings into given folder-of-tests and there will be many. which makes the maintenance harder. PR is here: https://github.com/jbosstools/jbosstools-build/pull/256

2) disable itests by default, and keep itests configuration in ITests profile. Advantage is that the build won't take ages by default (itests disabled), itests configuration is stored in ITests profile (don't need to copy everything to all folders-of-tests). To run the build with itests you need to call: `mvn verify -PITests` PR is here: https://github.com/jbosstools/jbosstools-build/pull/255

[~nickboldt], [~jeffmaury]. Please look at the PRs, review, comment and pick one preferred option.

Thanks!

> Refactor ITests settings in parent pom
> --------------------------------------
>
>                 Key: JBIDE-24547
>                 URL: https://issues.jboss.org/browse/JBIDE-24547
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: build, integration-tests
>            Reporter: Pavol Srna
>            Assignee: Pavol Srna
>             Fix For: 4.5.0.AM1
>
>
> It is desired that single 'mvn clean verify' command will run *unit tests* and *integration tests* in a single run. Parent pom should hold all shared settings across jbosstools repositories (e.g pluginCustomization, useUIThread etc ).
> The problem is that unit tests require useUIThread=true, but integration tests the opposite. We need to come with a solution where we share the settings in parent pom. 



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)