You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2007/01/21 23:02:22 UTC
[jira] Moved: (SUREFIRE-122) With forkmode once, XML reports are
cumulative
[ http://jira.codehaus.org/browse/SUREFIRE-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter moved MSUREFIRE-114 to SUREFIRE-122:
-------------------------------------------------
Affects Version/s: (was: 2.0 (2.2 plugin))
2.0 (2.2 plugin)
Fix Version/s: (was: 2.3)
2.3
Key: SUREFIRE-122 (was: MSUREFIRE-114)
Project: Maven Surefire (was: Maven 2.x Surefire Plugin)
> With forkmode once, XML reports are cumulative
> ----------------------------------------------
>
> Key: SUREFIRE-122
> URL: http://jira.codehaus.org/browse/SUREFIRE-122
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.0 (2.2 plugin)
> Reporter: Daniel Kulp
> Assigned To: Jason van Zyl
> Fix For: 2.3
>
> Attachments: XMLReporter-patch.txt
>
>
> 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