[
https://issues.apache.org/jira/browse/SUREFIRE-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16590686#comment-16590686
]
ASF GitHub Bot commented on SUREFIRE-1535:
------------------------------------------
Tibor17 commented on issue #190: [SUREFIRE-1535] Surefire unable to run testng
suites in parallel
URL: https://github.com/apache/maven-surefire/pull/190#issuecomment-415528689
@andreybpanfilov
I will push this to master because here is a chance that the integration
test 1177 will pass again.
My solution is in the branch
`https://gitbox.apache.org/repos/asf?p=maven-surefire.git;a=shortlog;h=refs/heads/V30_SUREFIRE-1535`
but I cannot use it now because it breaks the backwards compatibility. Pushing
it would be possible in version 3.0 and there I can break more, which means
using one property in Surefire Properties instead of multiple ones like a list
of classes `class.0`. One more thing which needs to be broken is the interface
of Surefire Provider class because this has two purposes and we serialize a
lots of objects useless which slows down the execution. So there is quite a lot
to do and to be consistent and having complete work done we would have to
accept this PR as a temporary solution and complete the work in version 3.0.
----------------------------------------------------------------
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:
[email protected]
> 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
(v7.6.3#76005)
