Repository navigation
test(gpuix): repair native regression checks - #6
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.
The desktop regression suite was failing on outdated view order, labels, geometry, and sync arguments, plus native test setup and transient paint-log assertions. Update those expectations, include Graph and accessible scrollbars in navigation checks, inject backup flush failures at the current runtime boundary, and dispose native test windows after exit autosave.
Native probes now set their window appearance and exercise scrolling from either boundary. Packaged launch verifies mounted onboarding content and waits for a nonblank native screenshot, avoiding cached-frame text-log races. Application behavior is unchanged; these test-only corrections need no changeset.
Validation on macOS:
Follow-up to #4.