mcpbeat

Playwright CI

zebbern/playwright-ci

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.

37k tokens
context cost
the whole folder, loaded on every use
10
files
instructions only
0
copies elsewhere
how many repositories repackaged it
4468
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/zebbern/claude-code-guide --skill playwright-ci

What comes with it

147 155 bytes besides the instruction
ci-github-actions.md
ci-gitlab.md
ci-other.md
docker-and-containers.md
global-setup-teardown.md
parallel-and-sharding.md
projects-and-dependencies.md
reporting-and-artifacts.md
test-coverage.md

The instruction itself

6 sections, as written by the author

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: 2 in CI only — surface flakiness in pipelines, not locally
  • traces: 'on-first-retry' — capture rich debugging artifacts without slowing every run
  • Shard across runners--shard=N/M splits tests evenly; scale horizontally, not vertically
  • Cache browser binaries~/.cache/ms-playwright keyed on Playwright version
  • Upload artifacts on failure — traces, screenshots, and HTML reports as CI artifacts
  • Use the official Docker imagemcr.microsoft.com/playwright:v* has all OS deps pre-installed
  • Global setup for auth — run login once in globalSetup, reuse storageState across 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 |

How to use it

Copy the folder

Take zebbern/playwright-ci from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.