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

Pavol Srna (JIRA) issues at jboss.org
Fri Jun 9 08:54:00 EDT 2017


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

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

[~nickboldt], I know that it's easy to define (and override) the settings in the root pom of the given folder-of-tests. However it's a bit unpractical, because with every change in the settings (plugin customization, some special property etc) we will need to maintain the settings in multiple places. Which is not much desired. We were thinking if maybe we can use maven phases and set different settings based on the phase. Not sure if that is even possible, will need to investigate a bit.

[~rob.stryker] I do not assume all UI / reddeer tests are integration tests. But I assume that the reddeer tests run with useUIThread = false. However your junit tests probably useUIThread = true. I haven't checked that in your (AS) plugins. But it's the case in e.g. hibernate tests.

> 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)


More information about the jbosstools-issues mailing list