Nest taxonomy and config in report schema v3#840
Merged
Conversation
6a352f2 to
40c7fbb
Compare
This comment has been minimized.
This comment has been minimized.
40c7fbb to
04589f2
Compare
This comment has been minimized.
This comment has been minimized.
04589f2 to
120a7e3
Compare
This comment has been minimized.
This comment has been minimized.
120a7e3 to
080c2a9
Compare
devpow112
commented
May 25, 2026
Comment on lines
+63
to
+66
| "taxonomy": { | ||
| "tool": "<Non-empty string matching pattern '^(?!\\s).+(?<!\\s)$', optional>", | ||
| "type": "<Non-empty string matching pattern '^(?!\\s).+(?<!\\s)$', optional>" | ||
| }, |
Contributor
Author
There was a problem hiding this comment.
@waikilee can you confirm we don't care about experience anymore. I thought we dropped that and just cared about tool, just double checking. If we still care I'll add it back and just have it nested.
Contributor
There was a problem hiding this comment.
Chatted with Waiki offline, he confirmed we don't care about the experience anymore - just the tool
Contributor
Coverage ReportReportReport Validation
|
Contributor
Author
|
Still have 1 more set of changes around report configuration that I want to make but it's reliant on the answer to #840 (comment) |
sarahboyd
approved these changes
May 25, 2026
|
🎉 This PR is included in version 5.2.6 🎉 The release is available on: Your semantic-release bot 📦🚀 |
devpow112
added a commit
that referenced
this pull request
May 25, 2026
devpow112
added a commit
that referenced
this pull request
May 25, 2026
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.
QE-651
Reshapes report schema v3 so taxonomy-related and config-related fields are grouped under nested objects on each test detail, and removes
experiencefrom the report entirely.Report schema v3 changes (vs in-flight v3)
toolandtypemoved from top-level detail into a nestedtaxonomyobjecttimeoutmoved from top-level detail into a nestedconfigobjectexperienceremoved from test detailReport schema v3 changes (vs v2)
toolandtypemoved from top-level detail into a nestedtaxonomyobjecttimeoutmoved from top-level detail into a nestedconfigobjectexperienceremoved from test detailgithub.codeownerson test detail