test(e2e): browser signup lands on a workspace and creates a first workbench (CL-9567) - #1006
Merged
Merged
Conversation
TheGreatAxios
enabled auto-merge (squash)
September 30, 2026 05:38
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.
Summary
e2e/browser/first-run.test.ts: a fresh user signs up in real Chrome, the client provisions its workspace over stock routes, connects an Anthropic placeholder key (stored only, never called), lands on the new-workbench prompt, starts a workbench, and sees it in the sidebar Workbenches group. UI-visible assertions only.Bugs found
PORTunset. Noapps/webbug found; the flow works end to end.alice+<ts>@example.com. A workspace with no workbenches lands directly on/new.Workflow probe cleanupreconciliation errors and sidecar WebSocket reconnect warnings after the test.Resolves CL-9567