[
http://jira.codehaus.org/browse/SUREFIRE-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85726
]
Robert Watkins commented on SUREFIRE-122:
-----------------------------------------
For anyone else who stumbles upon this, the workaround above (using the 2.1.3
plugin) has its own set of issues.
The default values of a few of the configuration arguments for the surefire
plugin changed between 2.1.3 and 2.2. The two I've come across were:
* forkmode (defaults to 'once' in 2.2, but 'none' in 2.1.3)
* childDelegation (defaults to 'false' in 2.2, but 'true' in 2.1.3)
The changes in these defaults can cause issues (I got OOM errors and problems
with the XML classloaders) that are somewhat hard to diagnose, partially
because the 2.2 plugin documentation doesn't indicate that the defaults had
changed between versions. (For example, the only reason I noticed the forkmode
problem is because I was dumping the running Java processes in order to
diagnose the OOM).
> 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
