[
https://jira.codehaus.org/browse/SUREFIRE-797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=331160#comment-331160
]
Tibor Digana edited comment on SUREFIRE-797 at 8/20/13 6:11 AM:
----------------------------------------------------------------
@Jonatan Jönsson
The surefire 2.16 went out.
Now if you specify <parallel>methods</parallel> and a suite is in <includes/>
or <test />, only the methods of classes included in the suite will run in
parallel.
You can nowadays use combinations of suites, classes, and methods to run them
in parallel and configure thread resources.
I am working on a next release which will calculate and optimize thread
resources upon the total thread count, the amount of suites, classes and
methods to gain the performance of your tests.
was (Author: tibor17):
@Jonatan Jönsson
The surefire 2.16 went out.
Now if you specify <parallel>methods</parallel> and a suite is in <includes/>
or <test />, the methods of classes included in the suite will run in parallel.
You can nowadays use combinations of suites, classes, and methods to run them
in parallel and configure thread resources.
I am working on a next release which will calculate and optimize thread
resources upon the total thread count, the amount of suites, classes and
methods to gain the performance of your tests.
> Parallel junit does not run in parallel when a Suite is used at the top level
> -----------------------------------------------------------------------------
>
> Key: SUREFIRE-797
> URL: https://jira.codehaus.org/browse/SUREFIRE-797
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.7+ (parallel) support
> Affects Versions: 2.6, 2.7, 2.8, 2.9, 2.10
> Reporter: Kristian Rosenvold
> Fix For: Backlog
>
>
> Using the test project at
> maven-surefire/surefire-integration-tests/src/test/resources/junit47-parallel-with-suite
> one can see that the actual tests do not get run in parallel. This is due to
> the project running a top-level suite.
> I have researched this a little bit, and it seems like this does not even
> work with regular JUnit (even without our special runners), so the problem
> may be theirs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
