[
https://jira.codehaus.org/browse/SUREFIRE-1149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=364939#comment-364939
]
Tibor Digana commented on SUREFIRE-1149:
----------------------------------------
Run
mvn help:effective-pom > log.txt
and have a look in log.txt what junit version is used - let us know.
If you remove dependenciesToScan, is the running in parallel?
Which failsafe version worked in this example?
I don't understand how you use this POM.
In first part of the description you say that does fork, and finally this forks:
mvn failsafe:integration-test -DforkCount=3
So what's the difference in forking mode without parameter <parallel/> ?
> Tests from dependency jar ignore parallel execution
> ---------------------------------------------------
>
> Key: SUREFIRE-1149
> URL: https://jira.codehaus.org/browse/SUREFIRE-1149
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.7+ (parallel) support, Maven Failsafe Plugin,
> Maven Surefire Plugin, process forking
> Affects Versions: 2.18.1
> Reporter: Christopher Smith
> Attachments: pom.xml
>
>
> I have a Selenium test suite that is contained in a module of my main
> application but that needs to be run against an instance deployed to a
> staging environment. I package the tests into a jar and have a separate POM
> that declares {{dependenciesToScan}} and is executed in a later CI step. The
> tests execute, but the runner completely ignores any parallel configuration:
> neither {{parallel}} nor {{forkCount}} has any effect. The debug log shows
> that the plugin is switching to parallel mode, but then it runs them serially
> in a single Java process. As these are browser-driving tests, serial
> execution drastically increases running time.
> Running the tests directly from the main project tree using {{mvn
> failsafe:integration-test -DforkCount=3}} forks multiple JVMs and executes
> the tests in parallel.
> The attached POM is the one used to execute the tests after deployment, and
> which ignores parallel execution for test from the jar.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
