Claude Skill MartBrowse skillsQuick linesLearn by videoTerminal guideWhat is a Skill?
 
← Back to list

Playwright CI/CD Playbook

Battle-tested configuration patterns for running Playwright tests fast and reliably on GitHub Actions, GitLab CI, Docker, and other CI providers.

Dev & CodingIntermediate★ 383⑂ 62AI score 7/10Last updated: Sep 6, 2026

What it does

Collects the practical setup you need when moving Playwright E2E tests into a CI pipeline.

  • 8 golden rules: retries: 2 in CI only, trace: 'on-first-retry', horizontal scaling with --shard=N/M, caching ~/.cache/ms-playwright by Playwright version, uploading artifacts on failure, using the official mcr.microsoft.com/playwright:v* image, and logging in once in globalSetup to reuse storageState
  • Per-provider guides: GitHub Actions, GitLab CI, CircleCI / Azure DevOps / Jenkins
  • Execution & scaling: parallelism and sharding, Docker/containers, multi-project config and dependencies
  • Reporting & setup: reports and artifacts, code coverage, global setup/teardown

Who it's for

  • Developers whose Playwright suite works locally but isn't reliably wired into CI yet
  • QA/platform engineers trying to cut pipeline time by sharding across runners
  • Teams that need traces, screenshots, and HTML reports to debug flaky tests

Example uses

  1. "Generate a GitHub Actions workflow that runs Playwright across 4 shards" → sharding matrix, browser cache, merged reports
  2. "Update playwright.config.ts so retries and traces only kick in on CI" → CI-conditional config branch
  3. "Move login into globalSetup and reuse storageState across workers" → global setup script plus project dependencies

· · · Install guide · · ·

Try it now, no install

Paste this into Claude to use the skill without installing anything.

Read the instructions in this file and follow them to help me:
https://raw.githubusercontent.com/testdino-hq/playwright-skill/HEAD/ci/SKILL.md

What I want: (describe your task here)

If Claude can't open the link, open it yourself and paste the contents instead.

↓ If it works for you, download the ZIP below and install it. Then it runs on its own — no pasting each time.

Install in the Claude app (no terminal)
  1. Download the ZIP with the button below.
  2. In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
  3. Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
↓ Download ZIP
Install in Claude Code

Let Claude do it — paste this into Claude Code

Install the skill I found on Claude Skill Mart.
Copy the ci folder from the GitHub repo testdino-hq/playwright-skill into my ~/.claude/skills/playwright-ci/.
When it's done, tell me in one line what this skill can do.

Install with a command instead

git clone https://github.com/testdino-hq/playwright-skill.git /tmp/playwright-skill && mkdir -p ~/.claude/skills/playwright-ci && cp -r /tmp/playwright-skill/ci/* ~/.claude/skills/playwright-ci/

⚠ This is a third-party skill. Check the source repository before installing.

  1. Open a terminal.
  2. Clone the repository into a temp folder: git clone https://github.com/testdino-hq/playwright-skill.git /tmp/playwright-skill
  3. Create the skill directory: mkdir -p ~/.claude/skills/playwright-ci
  4. Copy everything from the ci folder (SKILL.md plus the nine guide files): cp -r /tmp/playwright-skill/ci/* ~/.claude/skills/playwright-ci/
  5. Verify with ls ~/.claude/skills/playwright-ci — you should see files like ci-github-actions.md; without them the in-document links break.
  6. Restart Claude Code, then try a prompt such as "Set up Playwright sharding in GitHub Actions."
View source on GitHub ↗License: MIT