Add durable settings browser test suite#5773
Draft
BillLeoutsakosvl346 wants to merge 2 commits into
Draft
Conversation
Allow focused child PRs to receive normal CI before the completed suite returns to staging.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
* test(e2e): add reusable Playwright foundation Establish a hermetic full-stack browser harness so settings and future surfaces can exercise real authentication, APIs, and isolated database state safely. * test(e2e): harden runner lifecycle and artifacts Fail closed on stale processes, preserve cleanup during interruption, and keep credentials and personal fixture data out of uploaded diagnostics. * test(e2e): tighten isolation and shutdown guards Make destructive database operations and service bindings strictly local while ensuring interrupted runs fully stop managed children before cleanup. * test(e2e): finalize harness safety boundaries Close the remaining lifecycle, credential-isolation, and CLI escape hatches so future persona and settings suites can build on a fail-closed foundation. * test(e2e): harden interrupted-run cleanup Use a detached cleanup supervisor so repeated signals cannot interrupt process-group shutdown or forced removal of the guarded run database. * test(e2e): guard signal cleanup edge cases Prevent empty process-group targets and verify forced-drop retries against final database state so interrupted runs cannot self-signal or report false cleanup failures. * test(e2e): require exact host and race-safe signals Reject dual-stack host mappings that cannot reach IPv4-only services and tolerate child exit races during process-group signal fallback. * test(e2e): force IPv4 for hosted test origin Accept safe dual-stack loopback resolution while pinning Chromium and Node traffic to 127.0.0.1 so CI reaches IPv4-only services reliably. * test(e2e): settle readiness exit race Mark successful readiness before the managed process completion branch can reject, preventing later normal shutdown from surfacing an abandoned promise failure. * test(e2e): propagate IPv4 preference to probes Keep Node-based Playwright requests on the same IPv4 path as Chromium and use direct loopback for orchestrator probes under dual-stack CI DNS. --------- Co-authored-by: Bill Leoutsakos <billleoutsakos@Bills-MacBook-Pro.local>
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
Delivery plan
Test plan
This is the draft integration PR. Each delivery step will be reviewed in a focused PR targeting
e2e/settings-playwrightbefore this PR is made ready for final review.Made with Cursor