ASF GitHub Bot commented on SUREFIRE-1535:

Tibor17 edited a comment on issue #190: [SUREFIRE-1535] Surefire unable to run 
testng suites in parallel
URL: https://github.com/apache/maven-surefire/pull/190#issuecomment-404166769
   Pls explore the following.
   I expected these two `FORKTESTSET`, `TEST_SUITE_XML_FILES` been exclusive. 
Not sure if this is a fix or a workaround because in this commit we passed the 
value from variable `testSet` into `properties.addList`.
   Question, should the `testSuiteDefinition.getSuiteXmlFiles()` be already 
filled up with value and then `testSet` become null? Here we interchanged these 
two, but mabe the (pre)caller of BooterSerializer should detect this situation 
with XML Suites.

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> 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
>            Priority: Minor
> 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

Reply via email to