feat!: [junit] capture test case level out, error and attachments #136
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In v5.x and later, system-out and system-err logs are reported at a per testcase element in the report. Because each test adapter determines to also emit the console output and errors at test suite level, there may be some duplication for the messages.
v4.x and earlier behavior
Prior to v5.x, console stdout and stderr was reported only in the system-out and system-err elements at testsuite level. This would concatenate messages from all test results and information messages from adapter.
To disable output in reports: see https://github.com/spekt/testlogger/blob/master/src/JUnit.Xml.Package/README.md#storeconsoleoutput.
Fixes spekt/junit.testlogger#71, spekt/junit.testlogger#41, spekt/junit.testlogger#40, #130