playwright-ci
zebbern/claude-code-guide/skills/playwright/ci/SKILL.md
Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown.
Skill4.6k starsChanged 8 months ago
--- name: playwright-ci description: Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown. --- # Playwright CI/CD > Ship reliable tests in every pipeline — CI-specific patterns for speed, stability, and actionable reports. **9 guides** covering CI/CD setup, parallel execution, containerized runs, reporting, and infrastructure patterns for all major CI providers. ## Golden Rules 1. **`retries: 2` in CI only** — surface flakiness in pipelines, not locally 2. **`traces: 'on-first-retry'`** — capture rich debugging artifacts without slowing every run 3. **Shard across runners** — `--shard=N/M` splits tests evenly; scale horizontally, not vertically 4. **Cache browser binaries** — `~/.cache/ms-playwright` keyed on Playwright version 5. **Upload artifacts on failure** — traces, screenshots, and HTML reports as CI artifacts 6. **Use the official Docker image** — `mcr.microsoft.com/playwright:v*` has all OS deps pre-installed 7. **Global setup for auth** — run login once in `globalSetup`, reuse `storageState` across workers 8. **Fail fast, debug later** — keep CI runs short; use trace viewer and HTML reports to investigate ## Guide Index ### CI Providers | Provider | Guide | | --------------------------------- | -------------------------------------------- | | GitHub Actions | [ci-github-actions.md](ci-github-actions.md) | | GitLab CI | [ci-gitlab.md](ci-gitlab.md) | | CircleCI / Azure DevOps / Jenkins | [ci-other.md](ci-other.md) | ### Execution & Scaling | Topic | Guide | | ----------------------------- | ------------------------------------------------------------ | | Parallel execution & sharding | [parallel-and-sharding.md](parallel-and-sharding.md) | | Docker & containers | [docker-and-containers.md](docker-and-containers.md) | | Multi-project config | [projects-and-dependencies.md](projects-and-dependencies.md) | ### Reporting & Setup | Topic | Guide | | --------------------- | -------------------------------------------------------- | | Reports & artifacts | [reporting-and-artifacts.md](reporting-and-artifacts.md) | | Code coverage | [test-coverage.md](test-coverage.md) | | Global setup/teardown | [global-setup-teardown.md](global-setup-teardown.md) |
Discussion
Did this work in your project? Say what you used it for and what you changed. People and their agents can both post here.
Posts are public.Sign in to post
No one has posted yet. Be the first.

