[
https://jira.codehaus.org/browse/SUREFIRE-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Rosenvold closed SUREFIRE-882.
---------------------------------------
Resolution: Fixed
Fix Version/s: 2.13
Assignee: Kristian Rosenvold
Fixed in separate issue
> Fork x parallel JVMs once
> -------------------------
>
> Key: SUREFIRE-882
> URL: https://jira.codehaus.org/browse/SUREFIRE-882
> Project: Maven Surefire
> Issue Type: New Feature
> Components: process forking
> Affects Versions: 2.12
> Reporter: Falko Modler
> Assignee: Kristian Rosenvold
> Fix For: 2.13
>
>
> In 2.12 a new forkMode "perthread" was introduced, which (in conjunction with
> parallel!=none) behaves like a parallel "always"-forkMode.
> So for instance parallel=classes and forkMode=perthread fork x JVMs in
> parallel, whereas each JVM executes just one(!) test class and then
> terminates.
> It would come in handy if there was another new forkMode (like
> "perthreadOnce" or similar) which forks x JVMs that keep on executing test
> classes (parallel=classes) until there are no more test-classes left to
> execute.
> Example (all with parallel=classes and threadCount=2) with 4 test classes
> (Test1-4):
> perthread:
> JVM1 is forked for Test1
> JVM2 is forked for Test2
> JVM1 for Test1 terminates
> JVM2 for Test2 terminates
> JVM3 is forked for Test3
> JVM4 is forked for Test4
> JVM4 for Test3 terminates
> JVM3 for Test3 terminates
> perthreadOnce (or the like):
> JVM1 is forked, executes Test1
> JVM2 is forked, executes Test2
> JVM1 executes Test3
> JVM2 executes Test4
> JVM1 terminates
> JVM2 terminates
> In reality, the order of events can differ of course.
--
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
