Repository navigation
test(e2e): wait for hydration before dev overlay recovery click - #2410
Merged
james-elicx merged 1 commit intoJun 29, 2026
Merged
james-elicx merged 1 commit into
james-elicx merged 1 commit into
Conversation
The dev overlay recovery spec armed its reload canary after only confirming that the navigation runtime existed. That was not enough to prove the app-router client tree had hydrated the Link handler, so CI could occasionally follow the anchor as a hard navigation before the soft-nav path was ready. Reuse the shared app-router hydration helper before setting the canary and clicking the recovery link. The test still exercises the real browser click path, but no longer races client hydration.
commit: |
Contributor
Performance benchmarksCompared 0 improved · 0 regressed · 6 within ±1.5%
View detailed results and traces 🟢 improvement · 🔴 regression · ⚫ change below 1.5% · paired base/head |
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.
Fixes #2409
Overview
The
app-with-srcdev overlay recovery E2E now waits for the shared App Router hydration signal before setting the reload canary and clicking the recoveryLink.Why
The flaky failure was a real test race: the previous wait only proved that the navigation runtime object existed. It did not prove React had hydrated the client tree that intercepts the
Linkclick, so CI could occasionally perform a hard navigation before the soft-nav path was ready.What changed
waitForAppRouterHydration(page).Validation
PLAYWRIGHT_PROJECT=app-with-src vp exec playwright test tests/e2e/app-with-src/dev-overlay-recovery.spec.ts --project=app-with-src --repeat-each=10 --retries=0PLAYWRIGHT_PROJECT=app-with-src vp exec playwright test --project=app-with-src --retries=0vp check tests/e2e/app-with-src/dev-overlay-recovery.spec.ts