Fix the JUnit 5 XML output #246
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
shs96c
requested changes
Feb 9, 2024
...urefire-reports/TEST-com.github.bazel_contrib.contrib_rules_jvm.comparative.DynamicTests.xml
Outdated
Show resolved
Hide resolved
...t/surefire-reports/TEST-com.github.bazel_contrib.contrib_rules_jvm.comparative.MixedTest.xml
Outdated
Show resolved
Hide resolved
...re-reports/TEST-com.github.bazel_contrib.contrib_rules_jvm.comparative.ParameterisedTest.xml
Outdated
Show resolved
Hide resolved
THe output for the Junit5 XML did not match the output from the Gradle (our gold standard) or Maven (a secondary goal). This took digging further into the JUnit internal test setup and deciphering how each test is processed, and pushing it back into the form we want it in. It would be nice if JUnit itself did this but ...
tjoneslo
force-pushed
the
Update-junit5-xml-output
branch
from
8fae09e to
5fd3b10
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
THe output for the Junit5 XML did not match the output from the Gradle (our gold standard) or Maven (a secondary goal). This took digging further into the JUnit internal test setup and deciphering how each test is processed, and pushing it back into the form we want it in. It would be nice if JUnit itself did this but ...