Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
2.22.0
-
None
Description
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:
<forkCount>2</forkCount>
<reuseForks>false</reuseForks>
<suiteXmlFiles>
<suiteXmlFile>Suite_1.xml</suiteXmlFile>
<suiteXmlFile>Suite_2.xml</suiteXmlFile>
</suiteXmlFiles>
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.
Attachments
Issue Links
- links to