E2E in Staging CI
Overview
E2E runs in staging in two ways: (1) a validate-e2e job in the Staging Orchestrator (lint + typecheck only), and (2) E2E test steps inside the Next.js, Storybook, and Web Docs staging workflows after each app is built and (where applicable) started or deployed.
Where E2E runs in staging
| Workflow | E2E step |
|---|---|
| Staging Orchestrator | validate-e2e job: lint and typecheck @kartuli/e2e (no Playwright run). |
| Staging – Next.js app | After build (and optional Vercel deploy): runs smoke E2E for the target (game-client or backoffice-client). If deploy_target is vercel, passes VERCEL_PROTECTION_BYPASS_SECRET so tests can hit the preview URL. |
| Staging – Storybook | After build and preview: runs E2E smoke for tests/storybook with BASE_URL=http://localhost:6006. |
| Staging – Web Docs Client | After build and preview: runs E2E smoke for tests/web-docs-client with BASE_URL=http://localhost:4173. |
Triggers
- All of the above run on pull request targeting
mainwhen the orchestrator runs and the corresponding app/tool is affected (or, for validate-e2e, every PR that runs the orchestrator).
References
- E2E Hub
- E2E in Production CI
- Staging pipelines
- GitHub Actions CI/CD — Secrets (Vercel protection bypass secrets)