Adds support for writing supplemental junitxml reports #471
+192
−2
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.
fixed #232
deprecates #432
This PR allows a user to write a JUnitXML representation of report core report content at some location on their filesystem by passing in that desired path to a new
--write-junitxml-to
flag.This is designed to allow for the conversion of a report on verification to this output format, and write that to the filesystem. I.e.
chart-verifier verify
can be configured to produce this artifact, but this artifact has no meaning to thechart-verifier report
command, and the junitxml does not replace existing YAML/JSON report formats.Failing to write this report is considered non-fatal at the time of this writing.