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.
MCP get_skill({ skillId: "playwright-ci-cd-1da6e899" })Use this skill with your agent
Create a free account and connect via MCP
# 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) |
Related Skills
More skills in DevOps & Cloud
1password Skill
1password Skill linked from Juliano Barbosa Claude Code Skills, with the upstream skill instructions available on GitHub.
Actions Manager
GitHub Actions command center -- view workflow runs, read logs, re-run failed jobs, manage workflows, and debug CI failures entirely from the editor. Bypasses the deeply nested, visually-dependent Actions UI that is largely inaccessible to screen readers.
Airunway Aks Setup
Set up AI Runway on AKS — from bare cluster to running model. Covers cluster verification, controller install, GPU assessment, provider setup, and first deployment. WHEN: "setup AI Runway", "onboard AKS cluster", "install AI Runway", "airunway setup", "deploy model to AKS", "GPU inference on AKS", "KAITO setup on AKS", "run LLM on AKS", "vLLM on AKS", "set up model serving on AKS", "AI Runway controller".
Alz Accelerator
Deploy Azure Landing Zones using the ALZ Accelerator with AVM (Azure Verified Modules). Use this skill whenever the user mentions Azure Landing Zones, ALZ, Azure landing zone accelerator, AVM modules for landing zones, deploying management groups, hub-and-spoke networking, Virtual WAN, platform landing zones, or asks about Bicep vs Terraform for Azure infrastructure. Also trigger when the user wants to bootstrap CI/CD for Azure platform deployment, set up management groups hierarchy, or deploy connectivity/identity/management platform subscriptions.
Alz Accelerator Skill
Alz Accelerator Skill linked from Juliano Barbosa Claude Code Skills, with the upstream skill instructions available on GitHub.
Ansible Conventions and Best Practices
Ansible conventions and best practices
Explore Other Categories
Skills from other categories with shared topics
Browser Automation with playwright-cli
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.
Playwright Core
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.
Playwright Migration
Step-by-step migration guides for moving to Playwright from Cypress or Selenium/WebDriver — command mappings, architecture changes, and incremental adoption strategies.