playwright-ci
Skill393 starsChanged 31 days agoMITView on GitHub
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.
2 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- zebbern/claude-code-guideedited, first seen Oct 30, 2026
- jovd83/playwright-skilledited, first seen Sep 28, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 2
- zebbern/claude-code-guide★ 4.7k100% same
- jovd83/playwright-skill★ 118% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- playwright-coreSkill
- playwright-frontendSkill
- playwright-migrationSkill
- playwright-cliSkill
- playwright-pomSkill
- playwright-qaSkill
- playwright-skillSkill
The file
Files
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
retries: 2in CI only — surface flakiness in pipelines, not locallytraces: 'on-first-retry'— capture rich debugging artifacts without slowing every run- Shard across runners —
--shard=N/Msplits tests evenly; scale horizontally, not vertically - Cache browser binaries —
~/.cache/ms-playwrightkeyed on Playwright version - Upload artifacts on failure — traces, screenshots, and HTML reports as CI artifacts
- Use the official Docker image —
mcr.microsoft.com/playwright:v*has all OS deps pre-installed - Global setup for auth — run login once in
globalSetup, reusestorageStateacross workers - 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 |
| GitLab CI | ci-gitlab.md |
| CircleCI / Azure DevOps / Jenkins | ci-other.md |
Execution & Scaling
| Topic | Guide |
| Parallel execution & sharding | parallel-and-sharding.md |
| Docker & containers | docker-and-containers.md |
| Multi-project config | projects-and-dependencies.md |
Reporting & Setup
| Topic | Guide |
| Reports & artifacts | reporting-and-artifacts.md |
| Code coverage | test-coverage.md |
| Global setup/teardown | global-setup-teardown.md |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.