[
https://jira.codehaus.org/browse/SUREFIRE-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Hansen updated SUREFIRE-1055:
-----------------------------------
Description:
Some test methods are skipped at random with the below configuration. When test
methods are skipped in this way, only one method in the class runs. Running
tests repeatedly with no code change often yields a different number of tests
with each run (e.g. see the attached surefire-output.txt). Tests that take
longer to run are less likely to be affected. This affects version 2.16 of
Surefire and Failsafe equally.
Here is a simple test project which reproduces the issue:
https://github.com/hansenc/SUREFIRE-1055
It has a few simple test classes with a naming convention for how many test
methods are in each class (e.g. Methods4Test has 4 test methods).
{code:xml}
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>2.16</version>
<configuration>
<parallel>classesAndMethods</parallel>
<perCoreThreadCount>false</perCoreThreadCount>
<useUnlimitedThreads>true</useUnlimitedThreads>
<threadCountMethods>3</threadCountMethods>
</configuration>
</plugin>
{code}
was:
Some test methods are skipped at random with the below configuration. When test
methods are skipped in this way, only one method in the class runs. Running
tests repeatedly with no code change often yields a different number of tests
with each run (e.g. see the attached surefire-output.txt). This affects version
2.16 of Surefire and Failsafe equally.
Here is a simple test project which reproduces the issue:
https://github.com/hansenc/SUREFIRE-1055
It has a few simple test classes with a naming convention for how many test
methods are in each class (e.g. Methods4Test has 4 test methods).
{code:xml}
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>2.16</version>
<configuration>
<parallel>classesAndMethods</parallel>
<perCoreThreadCount>false</perCoreThreadCount>
<useUnlimitedThreads>true</useUnlimitedThreads>
<threadCountMethods>3</threadCountMethods>
</configuration>
</plugin>
{code}
> Parallel JUnit does not run all test methods with parallel=classesAndMethods
> perCoreThreadCount=false useUnlimitedThreads=true and threadCountMethods
> specified
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SUREFIRE-1055
> URL: https://jira.codehaus.org/browse/SUREFIRE-1055
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.7+ (parallel) support, Maven Failsafe Plugin,
> Maven Surefire Plugin
> Affects Versions: 2.16
> Reporter: Chris Hansen
> Attachments: surefire-output.txt
>
>
> Some test methods are skipped at random with the below configuration. When
> test methods are skipped in this way, only one method in the class runs.
> Running tests repeatedly with no code change often yields a different number
> of tests with each run (e.g. see the attached surefire-output.txt). Tests
> that take longer to run are less likely to be affected. This affects version
> 2.16 of Surefire and Failsafe equally.
> Here is a simple test project which reproduces the issue:
> https://github.com/hansenc/SUREFIRE-1055
> It has a few simple test classes with a naming convention for how many test
> methods are in each class (e.g. Methods4Test has 4 test methods).
> {code:xml}
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-surefire-plugin</artifactId>
> <version>2.16</version>
> <configuration>
> <parallel>classesAndMethods</parallel>
> <perCoreThreadCount>false</perCoreThreadCount>
> <useUnlimitedThreads>true</useUnlimitedThreads>
> <threadCountMethods>3</threadCountMethods>
> </configuration>
> </plugin>
> {code}
--
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
