[jira] Created: (MSUREFIRE-125) surefire xml report not wellformed on junit returning int

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] Created: (MSUREFIRE-125) surefire xml report not wellformed on junit returning int

JIRA jira@codehaus.org
surefire xml report not wellformed on junit returning int
---------------------------------------------------------

         Key: MSUREFIRE-125
         URL: http://jira.codehaus.org/browse/MSUREFIRE-125
     Project: Maven 2.x Surefire Plugin
        Type: Bug

    Versions: 2.1.2    
 Environment: Windows XP Pro, Java 1.5.0_06
    Reporter: Andreas Schödl
 Attachments: SurefireXmlTest.java, TEST-de.sag.dms.junit.SurefireXmlTest.xml, de.sag.dms.junit.SurefireXmlTest.txt

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:&lt;1&gt; but was:&lt;2&gt;

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

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (MSUREFIRE-125) surefire xml report not wellformed on junit returning int

JIRA jira@codehaus.org
    [ http://jira.codehaus.org/browse/MSUREFIRE-125?page=comments#action_66442 ]

Carlos Sanchez commented on MSUREFIRE-125:
------------------------------------------

have you tried surefire 2.1.3? I think this was already fixed

> surefire xml report not wellformed on junit returning int
> ---------------------------------------------------------
>
>          Key: MSUREFIRE-125
>          URL: http://jira.codehaus.org/browse/MSUREFIRE-125
>      Project: Maven 2.x Surefire Plugin
>         Type: Bug

>     Versions: 2.1.2
>  Environment: Windows XP Pro, Java 1.5.0_06
>     Reporter: Andreas Schödl
>  Attachments: SurefireXmlTest.java, TEST-de.sag.dms.junit.SurefireXmlTest.xml, de.sag.dms.junit.SurefireXmlTest.txt
>
>
> 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:&lt;1&gt; but was:&lt;2&gt;
> 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

Reply | Threaded
Open this post in threaded view
|

[jira] Closed: (MSUREFIRE-125) surefire xml report not wellformed on junit returning int

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org
     [ http://jira.codehaus.org/browse/MSUREFIRE-125?page=all ]
     
Andreas Schödl closed MSUREFIRE-125:
------------------------------------

     Resolution: Fixed
    Fix Version: 2.2

Is fixed in 2.2 (couldn't update to 2.1.3 to verify that release)

> surefire xml report not wellformed on junit returning int
> ---------------------------------------------------------
>
>          Key: MSUREFIRE-125
>          URL: http://jira.codehaus.org/browse/MSUREFIRE-125
>      Project: Maven 2.x Surefire Plugin
>         Type: Bug

>     Versions: 2.1.2
>  Environment: Windows XP Pro, Java 1.5.0_06
>     Reporter: Andreas Schödl
>      Fix For: 2.2
>  Attachments: SurefireXmlTest.java, TEST-de.sag.dms.junit.SurefireXmlTest.xml, de.sag.dms.junit.SurefireXmlTest.txt
>
>
> 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:&lt;1&gt; but was:&lt;2&gt;
> 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