Repository navigation
Validate actual browser reports and grouped observation cases - #21
Merged
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
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.
A successful 175-test browser run was rejected by
inspectReport()because three grouped-locator regression titles were missing from its strict engine-case list. Add the three exact titles and validate every actual browser JSON report in Linux and macOS CI before package consumers.Validation:
UNRECOGNIZED_ENGINE_CASEagainst the original Linux report from run 41316315577 (175 passed, no skips/flakes).The 100 ms threshold and zero retries remain unchanged. No final 100-round run or release is part of this change. Historical release evidence does not qualify this revision.