[
https://issues.apache.org/jira/browse/SUREFIRE-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana updated SUREFIRE-1535:
-----------------------------------
Fix Version/s: 2.22.1
> Surefire unable to run testng suites in parallel
> ------------------------------------------------
>
> Key: SUREFIRE-1535
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1535
> Project: Maven Surefire
> Issue Type: Bug
> Components: TestNG support
> Affects Versions: 2.22.0
> Reporter: Andrey Panfilov
> Assignee: Tibor Digana
> Priority: Minor
> Fix For: 2.22.1
>
>
> Due to slowness nature of selenium test we would like to run such tests in
> parallel, moreover, we also would like to avoid thread-safety issues, so our
> option is to take advantage of forkCount=N and reuseForks=false instead of
> using built-in testng capabilities. Unfortunately, when using following maven
> configuration:
> {code:java}
> <forkCount>2</forkCount>
> <reuseForks>false</reuseForks>
> <suiteXmlFiles>
> <suiteXmlFile>Suite_1.xml</suiteXmlFile>
> <suiteXmlFile>Suite_2.xml</suiteXmlFile>
> </suiteXmlFiles>
> {code}
> it does not work like expected, i.e.:
> * ForkStarter#runSuitesForkPerTestSet correctly spawns multiple JVMs and
> passes individual testng suite to ForkStarter#fork
> * TestNGProvider#invoke fails to cover the case that forkTestSet could be a
> file and runs all testng suites instead of individual one.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)