Group generated-output differences by test case - #3079
Merged
Conversation
No generated-output differences✅ This PR does not change generated outputs. |
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
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.
Change
Group generated files by their input test case instead of listing them in target-first path order.
Each test group now shows:
Search and target/status filters hide empty test groups, and the summary includes the number of affected test cases.
Live example
The existing #2983 report has been explicitly regenerated with this renderer. Its 95 generated files are now organized into the 3 actual affected test cases:
https://hostr.flingit.run/s/quicktype/output-diffs/pr-2983/4a414e28a17dfcad70829842b5cc016090602b27/444607b9d6138ea753ec0c50dcba1ce5bdb1054f/index.html
Verification
git diff --checkpass.