[
http://jira.codehaus.org/browse/SUREFIRE-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87741
]
Lilians Auvigne commented on SUREFIRE-52:
-----------------------------------------
With workaround {code:xml} <forkMode>always</forkMode>{code} or {code:xml}
<forkMode>pertest</forkMode>{code} , i have always the problem.
I am obliged to use version 2.2 because I use TestNG.
Why the patch is not applied, in 2.3-SNAPSHOT ?
> XML Reports include testcases from previous tests
> -------------------------------------------------
>
> Key: SUREFIRE-52
> URL: http://jira.codehaus.org/browse/SUREFIRE-52
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.0 (2.2 plugin)
> Reporter: bin zhu
> Priority: Minor
> Fix For: 2.3
>
> Attachments: patch.txt
>
>
> to reproduce
> 1. create the following JUnit tests:
> public class TestA extends TestCase {
> public void test1() {
> }
> }
> public class TestB extends TestCase {
> public void test2() {
> }
> 2. run 'mvn clean install'
> note that in TEST-TestB.xml includes testcase results from test1 and test2,
> even though TestB only has test2()
> <testsuite errors="0" skipped="0" tests="1" time="0" failures="0"
> name="TestB">
> ...
> <testcase time="0" name="test1"/>
> <testcase time="0" name="test2"/>
> </testsuite>
--
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
