Fix missing test results for facebook/jest CI runs in Azure Pipelines #9177
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
SimenB
approved these changes
Nov 14, 2019
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
A breaking change in
jest-junit8.0.0 (jest-community/jest-junit#101) caused test results to no longer appear for the facebook/jest CI pipeline in Azure Pipelines:Example run
The jest-junit reporter is used in facebook/jest CI runs to produce XML Junit files which feed the Tests UX in Azure Pipelines.
The breaking change replaced the
outputconfiguration option (used injest.config.ci.js) with separateoutputDirectoryandoutputNameoptions. Moving to jest-junit 9.0.0 (#9114) caused the problem to surface.Test plan
With this fix, test results are now appearing again in Azure Pipelines: