playwright-ci
This skill provides production-ready CI/CD configurations and patterns for Playwright test automation across GitHub Actions, GitLab CI, CircleCI, Azure DevOps, and Jenkins. Use it when setting up reliable browser testing pipelines, implementing parallel test execution with sharding, containerizing tests with Docker, configuring reporting and artifacts, or establishing shared authentication workflows across CI environments.
git clone --depth 1 https://github.com/testdino-hq/playwright-skill /tmp/playwright-ci && cp -r /tmp/playwright-ci/ci ~/.claude/skills/playwright-ciSKILL.md
# 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) |
Battle-tested Playwright patterns for writing, debugging, and scaling reliable test suites. Use when you need guidance for E2E, API, component, visual, accessibility, or security testing, plus CI/CD, CLI automation, page objects, and migration from Cypress or Selenium. TypeScript and JavaScript.
Battle-tested Playwright patterns for writing and debugging reliable E2E, API, component, visual, accessibility, and security tests. Use when you need locator strategy, assertions, fixtures, network mocking, auth flows, trace debugging, or framework recipes for React, Next.js, Vue, and Angular. TypeScript and JavaScript.
Step-by-step migration guides for moving to Playwright from Cypress or Selenium/WebDriver — command mappings, architecture changes, and incremental adoption strategies.
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or have explicit authorization to test.
Page Object Model patterns for Playwright — when to use POM, how to structure page objects, and when fixtures or helpers are a better fit.