Skip to main content

Published Updated

CI Guides for Playwright and SmartTests

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​

GuideWhat you'll learn
Playwright GitHub ActionsPlaywright sharding, parallel workers, Playwright report, 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 Run QA. Product detail: run SmartTests in CI.

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.