Maven Surefire

Bug into xml report generation

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Cannot Reproduce
  • Affects Version/s: None
  • Fix Version/s: 2.4
  • Component/s: xml generation
  • Labels:
    None
  • Environment:
    release 2.0 of maven-surfire-plugin
    mvn 2.0.4
  • Testcase included:
    yes
  • Number of attachments :
    4

Description

since 2-3 weeks i have wrong information into my junit test tun (mvn test for example)
In fact, the *.txt are right, but the corresponding xml file have wrong entry. i means additionnal testcase are present ninto the testcase section.
you can find exmple in attachement (ThreadWarningSystemTest for example). You can see that the error number are good (because read into the attribute of the first xml tag) but in several TestSuite, we have testcase form other testsuite.

I don't know if this errors comes from maven dependancies update.
What i am sure is:
1/ a little bit of source modification into my project since this error appears.
2/ no new maven dependancies into my project
3/ i use only ibilio/maven2 as repository.

This errors can'be shown on other projet and other not ...

I have a workaround to solve this issue but with low performance:
I use the option "fork per test" and the reports is right.
Maybe a way to be investigate can be the temporaly file created by the command line:

Forking command line: java -classpath
> C:\HOMEWARE\maven-2_local\org\apache\maven\surefire\surefire-api\2.0\surefire-api-2.0.jar;C:\HOMEWARE\maven-2_local\o
> rg\codehaus\plexus\plexus-utils\1.1\plexus-utils-1.1.jar;C:\HOMEWARE\maven-2_local\org\apache\maven\surefire\surefire-booter\2.0\surefire-booter-2.0.jar or
> g.apache.maven.surefire.booter.SurefireBooter C:\temp\surefire40840tmp C:\temp\surefire40841tmp

Any Idea ?
Thx
Christophe

Issue Links

This issue duplicates:
SUREFIRE-52 XML Reports include testcases from previous tests Minor Closed

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Nick Cunnah added a comment -

I am also seeing this same bug.
Again *.txt are ok but *.xml are also including results from previous test cases.

-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running TestB testB
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.125 sec
Running TestC testC
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.013 sec
Running TestA testA
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 sec

Results :
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0

[TEST-TestB.xml]
...
<testcase time="0.003" name="testB"/>

[TEST-TestC.xml]
...
<testcase time="0.003" name="testB"/>
<testcase time="0" name="testC"/>

[TEST-TestA.xml]
...
<testcase time="0.003" name="testB"/>
<testcase time="0" name="testC"/>
<testcase time="0.001" name="testA"/>

For further details see nick.zip attachment for the 3 very simple "helloworld" style tests (.java, .txt and .xml) files.

Cheers,

Nick

Show
Nick Cunnah added a comment - I am also seeing this same bug. Again *.txt are ok but *.xml are also including results from previous test cases. ------------------------------------------------------- T E S T S ------------------------------------------------------- Running TestB testB Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.125 sec Running TestC testC Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.013 sec Running TestA testA Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 sec Results : Tests run: 3, Failures: 0, Errors: 0, Skipped: 0 [TEST-TestB.xml] ... <testcase time="0.003" name="testB"/> [TEST-TestC.xml] ... <testcase time="0.003" name="testB"/> <testcase time="0" name="testC"/> [TEST-TestA.xml] ... <testcase time="0.003" name="testB"/> <testcase time="0" name="testC"/> <testcase time="0.001" name="testA"/> For further details see nick.zip attachment for the 3 very simple "helloworld" style tests (.java, .txt and .xml) files. Cheers, Nick
Hide
Permalink
Nick Cunnah added a comment -

Simle test cases and results.

Show
Nick Cunnah added a comment - Simle test cases and results.
Hide
Permalink
Antoine Levy-Lambert added a comment -

Hi,
I built maven-surefire-plugin from HEAD to run the testcases of ... ant and I also observed the same issue.

Regards,

Antoine

Show
Antoine Levy-Lambert added a comment - Hi, I built maven-surefire-plugin from HEAD to run the testcases of ... ant and I also observed the same issue. Regards, Antoine
Hide
Permalink
Brice Copy added a comment -

Could someone fix this and make it the default version of the plugin ? Because of this bug, the surefire reports are rather unreadable when building multiple modules

Show
Brice Copy added a comment - Could someone fix this and make it the default version of the plugin ? Because of this bug, the surefire reports are rather unreadable when building multiple modules
Hide
Permalink
Milos Volauf added a comment -

Hi.

I am also voting for this bug to be fixed.

Here is a hint for the fix:

in the module surefire-api, the class org.apache.maven.surefire.report.XMLReporter
should implement a method:

public void testSetStarting(ReportEntry report) throws ReporterException { super.testSetStarting(report); results.clear(); }

(before each start, previous result should be cleared. AbstractTextReporter does the same.)

I tried it locally and it works.

Can someone provide a guess when this fix could appear in the released plugin (e.g. maven-surefire-plugin version 2.2.1 or something) ?

Show
Milos Volauf added a comment - Hi. I am also voting for this bug to be fixed. Here is a hint for the fix: in the module surefire-api, the class org.apache.maven.surefire.report.XMLReporter should implement a method: public void testSetStarting(ReportEntry report) throws ReporterException { super.testSetStarting(report); results.clear(); } (before each start, previous result should be cleared. AbstractTextReporter does the same.) I tried it locally and it works. Can someone provide a guess when this fix could appear in the released plugin (e.g. maven-surefire-plugin version 2.2.1 or something) ?
Hide
Permalink
Andreas Ebbert-Karroum added a comment -

I cannot beleive that this bug is still unfixed, it basically makes surefire unusable with maven2!

Show
Andreas Ebbert-Karroum added a comment - I cannot beleive that this bug is still unfixed, it basically makes surefire unusable with maven2!
Hide
Permalink
Henri Yandell added a comment -

+1, this bug's bitten me a couple of times now [10000 tests? wow! *investigate*... ohhh].

Show
Henri Yandell added a comment - +1, this bug's bitten me a couple of times now [10000 tests? wow! *investigate*... ohhh].
Hide
Permalink
Dan Fabulich added a comment -

This got fixed at some point. Integration test checked in revision 597279.

Show
Dan Fabulich added a comment - This got fixed at some point. Integration test checked in revision 597279.

People

Vote (19)
Watch (15)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.