[
https://jira.codehaus.org/browse/SUREFIRE-797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=323692#comment-323692
]
Jonatan Jönsson commented on SUREFIRE-797:
------------------------------------------
Related to this issue is the fact that
org.apache.maven.surefire.common.junit4.JUnit4TestChecker#isValidJUnit4Test
does not check for suite() methods returning junit.framework.Test (for example
https://github.com/Softhouse/jargo/blob/master/jargo/src/test/java/se/softhouse/common/collections/CharacterTrieGuavaTest.java).
I noticed this for my project https://github.com/Softhouse/jargo when I stared
to use <parallel>methods</parallel>. You can observe the drop in number of
tests at https://jontejj.ci.cloudbees.com/job/jargo/ build #8 and #9.
> 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
