fix: align Maestro assertVisible timeout#653
Merged
Merged
Conversation
|
Size Report
Startup median (7 runs, lower is better):
Top changed chunks:
|
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
1 participant
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
Align Maestro
assertVisiblecompatibility with Maestro's normal assertion wait budget by using a 7s default instead of 5s.This lets suites rely on regular
assertVisiblefor ordinary post-navigation checks instead of addingextendedWaitUntiltimeouts for cases that should fit within the default assertion window.Validation
pnpm exec vitest run src/compat/maestro/__tests__/replay-flow.test.ts src/compat/maestro/__tests__/runtime-assertions.test.tspnpm check:quick