Publish xUnit test results (non-Helix) #41385
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Related: #40983
Summary
After consolidating the CI pipelines, I missed that we still run non-Helix tests (specifically, the TemplateEngine tests). These tests produce the standard xUnit test information that needs to get published to the pipeline, or else it won't report the actual test failures. I added the ability for a job to specify that it should publish the xUnit test results. This parameter will work for any other xUnit test jobs we may need to add in the future (if we don't Helix-ify them right away).
Thanks to @Forgind for pointing out this issue, seen in this pipeline run.