[
http://jira.codehaus.org/browse/SUREFIRE-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter moved MSUREFIRE-125 to SUREFIRE-62:
------------------------------------------------
Affects Version/s: (was: 2.1.2)
1.5.2 (2.1.2 plugin)
Fix Version/s: (was: 2.2)
2.0 (2.2 plugin)
Complexity: Intermediate
Key: SUREFIRE-62 (was: MSUREFIRE-125)
Project: Maven Surefire (was: Maven 2.x Surefire Plugin)
> surefire xml report not wellformed on junit returning int
> ---------------------------------------------------------
>
> Key: SUREFIRE-62
> URL: http://jira.codehaus.org/browse/SUREFIRE-62
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 1.5.2 (2.1.2 plugin)
> Environment: Windows XP Pro, Java 1.5.0_06
> Reporter: Andreas Schödl
> Fix For: 2.0 (2.2 plugin)
>
> Attachments: de.sag.dms.junit.SurefireXmlTest.txt,
> SurefireXmlTest.java, TEST-de.sag.dms.junit.SurefireXmlTest.xml
>
>
> Surefire XML reports are not well-formed, they contain unescaped "<" and ">"
> characters when JUnit reports a failed assertEquals(1,2) with int.
> Putting attached SurefireXmlTest into your tests directory brings XML-results
> like the attached.
> excerpt:
> <failure type="junit.framework.AssertionFailedError" message="expected:<1>
> but was:<2>">junit.framework.AssertionFailedError: expected:<1> but
> was:<2>
> As you see, the element content is properly escaped, but not the content of
> attribute "message".
--
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
