[test-qa-hourly] Align guest locked-tab E2E behavior#111
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Continuous QA run update (2026-07-14)Inspected
ChangeThe merged implementation now starts sign-in and returns before navigating when a guest clicks Strategy, Activity, or Account, but the main-branch smoke test still asserted navigation to those locked routes. This PR changes only that contradictory E2E step:
ValidationRequested focused command: pnpm --filter @zapengine/app test:e2e -- tests/e2e/smoke.spec.tsRequested broader commands: pnpm turbo run type-check lint test --filter=@zapengine/app
pnpm --filter @zapengine/app test:e2eLocal execution result: not run — the execution container could not resolve Auto-mergeNot enabled. Repository setting |
Continuous QA run update (2026-07-14)
|
Summary
/podcast.Why
PR #108 changed
BottomTabBarso locked guest tabs start the account connect flow and return before navigation. The main-branch smoke test still expected those clicks to navigate to authenticated routes, leaving implementation and CI assertions contradictory. This is the smallest test-only correction that protects the intended guest behavior without weakening any gate.Scope
Validation
Focused validation:
Broader validation when CI runs:
pnpm turbo run type-check lint test --filter=@zapengine/app pnpm --filter @zapengine/app test:e2eGitHub Actions is the source of truth for this run. Local checkout was unavailable because outbound DNS from the execution container could not resolve GitHub, so validation is delegated to the PR checks.