Track tasks and feature requests
Join 36 million developers who use GitHub issues to help identify, assign, and keep track of the features and bug fixes your projects need.
Sign up for free See pricing for teams and enterprisesJUnit test results import fail #927
Comments
jgebal
added
the
bug
label
May 23, 2019
jgebal
added this to the v3.1.7 milestone
May 23, 2019
jgebal
self-assigned this
May 23, 2019
jgebal
referenced this issue
May 23, 2019
Merged
Failure details in sonar test reporter are now CDATA #926
jgebal
closed this
in
#926
Jun 2, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
jgebal commentedMay 23, 2019
Describe the bug
ut_junit_reportercan produce invalid output on failing tests with long failure message.The error that we see in import of test results in Jenkins is:
Provide version info
Running on latest utPLSQL v3.1.6
Information about client software
Not relevant
To Reproduce
Have a test that is failing and produces more than 4000 chars of output data and be unlucky enough to get the
<string at 4000 chars so the reporter inserts a line break.Example:
Expected behavior
We should probably make the failure message as CDATA rather than escape the chars.