Stabilize Playwright approval assertion#27
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
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.
What changed
Accept both supported rendered phrasings of a rejected approval request in the Docker-lab Playwright flow.
Why
The test asserted one wording (
request rejected) while the UI can render the equivalentUser rejected request, causing a flaky CI-only failure after the web server started successfully.Validation
pnpm testCI=1 pnpm test:playwrightpnpm exec prettier --check tests/playwright/docker-lab-idor-flow.spec.tsThe preceding main repair also creates
.databefore Playwright starts, resolving the prior Mastra LibSQL startup failure.