We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I have observed this issue with junit-xml==1.8 and Jenkins 2.46.3. In case it matters I'm using xUnit plugin to publish Junit results.
junit-xml==1.8
2.46.3
Create a test case with a multi-line output or traceback, e.g.
stdout = "line1\nline2" traceback = "line1\nline2" tc = TestCase(name=name, classname=classname, stdout=stdout) tc.add_error_info(output=traceback)
In the test case details displayed in Jenkins the multi-line values are shown like
line1 line2
Based on the formatting of test cases in the xunit plugin, I assume the proper tag to be generated should be:
<system-out> line1 line2 </system-out>
The first line has an extra indentation:
That is caused by the indentation given to text of the relevant tag:
The text was updated successfully, but these errors were encountered:
Thanks @memoselyk - please submit a PR with tests if you'd like this behavior to change
Sorry, something went wrong.
No branches or pull requests
I have observed this issue with
junit-xml==1.8
and Jenkins2.46.3
.In case it matters I'm using xUnit plugin to publish Junit results.
Steps to reproduce
Create a test case with a multi-line output or traceback, e.g.
Expected behavior
In the test case details displayed in Jenkins the multi-line values are shown like
Based on the formatting of test cases in the xunit plugin, I assume the proper tag to be generated should be:
Actual behavior
The first line has an extra indentation:
That is caused by the indentation given to text of the relevant tag:
The text was updated successfully, but these errors were encountered: