[ http://jira.codehaus.org/browse/MSUREFIRE-114?page=comments#action_70477
]
Mark Chaimungkalanont commented on MSUREFIRE-114:
-------------------------------------------------
I also see this problem. It has *definitely* only started happening since 2.2.
If I add
{code:xml}
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>2.1.3</version>
</plugin>
{code}
Things start working again. The linked issue MSUREFIRE-149 has a test project
setup that seems to cause this problem consistently.
My experience re: the forkMode setting is that it happens less frequently with
forkMode == always, but it does still seem to happen
> With forkmode once, XML reports are cumulative
> ----------------------------------------------
>
> Key: MSUREFIRE-114
> URL: http://jira.codehaus.org/browse/MSUREFIRE-114
> Project: Maven 2.x Surefire Plugin
> Issue Type: Bug
> Affects Versions: 2.2
> Reporter: Daniel Kulp
>
> With forkmode set to once, the resulting XML files seem to include the test
> results of all the tests in the previous suites as well as it's own.
> pseudo example:
> ATest is run, it has 2 test methods. The ATest.xml report says 2 tests run
> and passed
> BTest is run, it has 2 test methods. The BTest.xml report says 4 tests run
> and passed.
> CTest is run, it has 3 test methods. The CTest.xml report says 7 tests run
> and passed.
> When we use cruisecontrol or other reporting tools, it then say 13 tests run
> and passed instead of 5. What's worse, if a test in ATest fails, it's
> listed as a failure in all the tests so you get 3 tests failed, not 1.
> Plus, it's harder to figure out which test suite reallly had the failure.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
