[
https://jira.codehaus.org/browse/SUREFIRE-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=285537#comment-285537
]
Kristian Rosenvold commented on SUREFIRE-799:
---------------------------------------------
This is a cool patch;) It needs a few minor modifications; I think the regular
"threadCount" parameter should be used, and the forkMode should be "perthread".
It also needs an integration test, you should be able to modify (or make a new
project based on)
surefire-integration-tests/src/test/resources/runorder-parallel and a test
implementation in XmlReporterRunTimeIT.
(I think you can just modify the existing to accept forkMode as a -D parameter
instead of hard-coding)
I will be releasing 2.11.1 soon, but I'll schedule this patch for 2.12 if you
fix this stuff.
> Allow test parallelisation when forkMode=always
> -----------------------------------------------
>
> Key: SUREFIRE-799
> URL: https://jira.codehaus.org/browse/SUREFIRE-799
> Project: Maven Surefire
> Issue Type: Improvement
> Components: process forking
> Affects Versions: 2.10
> Environment: all
> Reporter: nkeywal
> Attachments: surefire_799_212_trunk.patch
>
>
> Surefire already allows:
> - forking
> - parallelization within a JVM
> Mixing both features would mean forking multiple JVM instead of only one.
> It would allow to parallelize tests that need to be executed in a separate
> JVM (i.e.: with forkMode=always). Usually these tests take longer than the
> simple ones. In our case, 40% of the tests are executed in 4 minutes, the
> other 60% need two hours. So it's obviously more interesting to parallelize
> the former, but these ones need to fork.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
