E2E Testing in CI
Short answer
Parallel Playwright in GitHub Actions only stays green when Arrange is isolated per worker—not when specs share staging users. Pair CI sharding and trace artifacts with seed routes and @testchimp/playwright reporting on every PR.
Guides in this section
| Guide | What you'll learn |
|---|---|
| Playwright in GitHub Actions | Parallel workers, sharding, artifacts, and TestChimp reporter wiring |
CI without isolation fails
Turning on workers: 4 without per-run fixtures multiplies flakes. Fix world-state first, then scale CI.
Per-PR workflow: gate merges with /testchimp test so agents repair SmartTests when selectors drift—see QA on Autopilot. Product detail: run SmartTests in CI.
Related
Frequently asked questions
Should I parallelize before fixing flakes?
Usually no—parallelism exposes shared-data bugs. Add runId-scoped seeds and probe Assert, then increase workers.
Does TestChimp replace GitHub Actions?
No—TestChimp orchestrates tests in your repo and reports runs. You keep Playwright in Actions; add @testchimp/playwright for traceability and test-run history.