Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Fixed
-
2.15, 2.16
-
None
-
Patch
Description
JUnit XML report contains invalid XML characters in <system-out> and <system-err> content. The illegal characters handling defined in SUREFIRE-456 doesn't work since version 2.15. The problem is that EncodingOutputStream in StatelessXmlReporter does not convert the illegal XML characters to their string representation (e.g. 0 -> "0").
Please find attached a possible fix for this issue as well as extended test case that includes illegal XML characters in system-out and system-err content.
Attachments
Attachments
Issue Links
- is duplicated by
-
SUREFIRE-1022 <system-out> malformed XML
- Closed
-
SUREFIRE-1014 Unparsable test report XML when sysout contains invalid XML
- Closed