Gate Beta — preview deployment tests

Gates Alpha, Gamma, and Delta complete while the PR is fresh. Gate Beta then waits for the thing only your infrastructure knows: whether the change actually deployed. The pipeline enters a waiting_for_deployment state, and when your deploy provider’s webhook (Vercel, Railway, Netlify, or a manual ping) reports a successful deployment, Beta queues and runs your QualityMax Playwright tests against the live preview URL.

Flow

1. Alpha + Gamma + Delta finish synchronously; the run parks in waiting_for_deployment.
2. Your deploy provider builds the preview and calls the QualityMax deploy webhook.
3. On a successful deployment, Beta is dispatched and runs the project’s Playwright tests against the preview URL.
4. The GitHub check run is updated with the final result.

This is the only gate that tests the deployed artifact rather than the diff — it catches what compile-time gates cannot: runtime wiring, environment variables, build-time behavior, and integration with the hosting platform.

Verdicts

Beta failures are hard blocks. A Playwright suite that ran against a genuinely broken deployment is the strongest signal in the pipeline, so it fully fails the check.

When Beta skips

• The event has no PR number (a direct push).
• The repository is typed as a non-web app: CLI tool, TUI agent, library/SDK, docs/knowledge site, or API-only. Non-web repos have no preview deployment to test.