[
https://jira.codehaus.org/browse/SUREFIRE-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=316579#comment-316579
]
Jesse Glick commented on SUREFIRE-751:
--------------------------------------
Getting harder to keep track of the different thread-related options; what is
the interaction between {{parallel}} and {{forkmode="perthread"}}?
http://maven.apache.org/surefire/maven-surefire-plugin/examples/junit.html
mentions parallelism but not (in this context) forking.
> Support parallel/fork mode similar to http://maven-junit-plugin.kenai.com/
> --------------------------------------------------------------------------
>
> Key: SUREFIRE-751
> URL: https://jira.codehaus.org/browse/SUREFIRE-751
> Project: Maven Surefire
> Issue Type: New Feature
> Components: process forking
> Affects Versions: 2.9
> Reporter: Stephen Connolly
> Assignee: Kristian Rosenvold
> Fix For: 2.13
>
> Attachments: SUREFIRE-751-part1.patch, SUREFIRE-751-part2.patch
>
>
> The current parallel execution spawns one thread _per_class_
> When there is a large disparity between the number of tests in different
> classes, this can result in a longer execution time. This can often happen in
> GUI testing, where a couple of classes will contain a lot of long running
> (but low cpu) test cases, and the remaining classes run fast.
> See http://maven-junit-plugin.kenai.com/ for an attempt at solving this
--
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
