playwright-ci
Streamline end-to-end testing by integrating Playwright into your continuous integration workflows. This skill guides you through setting up automated browser tests on major CI/CD platforms, ensuring reliable test execution across your deployment pipeline.
playwright-ci helps you integrate Playwright into major CI/CD platforms including GitHub Actions, GitLab CI, CircleCI, Azure DevOps, and Jenkins. The skill provides step-by-step guidance for configuring automated browser tests within your deployment pipeline, ensuring tests run reliably whenever code is committed or deployed. You'll learn platform-specific configuration syntax and best practices for each service.
AI-generated summary based on this skill's SKILL.md
Install
testdino-hq/playwright-skill/ci
git clone https://github.com/testdino-hq/playwright-skill
cp -r playwright-skill/ci ~/.claude/skills/ciFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I set up Playwright tests in a CI/CD pipeline?
playwright-ci helps you integrate Playwright into major CI/CD platforms including GitHub Actions, GitLab CI, CircleCI, Azure DevOps, and Jenkins. The skill provides step-by-step guidance for configuring automated browser tests within your deployment pipeline, ensuring tests run reliably whenever code is committed or deployed. You'll learn platform-specific configuration syntax and best practices for each service.
What is the best way to configure parallel test execution and sharding to speed up CI runs?
playwright-ci covers techniques for distributing your test suite across multiple workers and machines to dramatically reduce overall execution time. The skill explains test sharding strategies that divide your test load efficiently, allowing you to run hundreds of tests concurrently rather than sequentially. This approach significantly accelerates your CI feedback loop while maintaining test isolation and reliability.
How can I containerize Playwright tests using Docker for consistent CI environments?
playwright-ci provides guidance on packaging Playwright tests in Docker containers to ensure your tests run identically across all environments—local machines, CI servers, and production deployments. The skill covers Dockerfile configuration, browser installation within containers, and orchestration patterns that eliminate environment-specific failures and make your test suite truly portable.
How do I generate and upload test reports, traces, screenshots, and coverage artifacts in my pipeline?
playwright-ci explains how to capture comprehensive test artifacts including HTML reports, execution traces, screenshots, and code coverage data, then upload them to your CI system or external storage. The skill shows you how to configure artifact retention policies, integrate with reporting dashboards, and use trace viewer for debugging failed tests directly from your CI logs.
What are the key strategies for optimizing CI performance through caching, retries, and global authentication setup?
playwright-ci teaches performance optimization techniques including browser binary caching to avoid repeated downloads, intelligent retry logic for flaky tests, and global setup/teardown patterns for shared authentication state. These strategies reduce CI execution time, lower bandwidth costs, and improve test reliability by reusing expensive resources across test runs.
What does playwright-ci cover regarding playwright storage state auth CI and best practices?
playwright-ci addresses how to manage authentication state efficiently in CI environments using storage state files, eliminating the need to log in repeatedly during test execution. The skill covers best practices for securely handling credentials, reusing authenticated sessions across test workers, and implementing global setup/teardown patterns that streamline your entire CI workflow while maintaining security and performance.
SKILL.md
rendered from the published skill — quoted content, verbatim
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
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 10 files
ci/SKILL.md
ci/ci-github-actions.md
ci/ci-gitlab.md
ci/ci-other.md
ci/docker-and-containers.md
ci/global-setup-teardown.md
ci/parallel-and-sharding.md
ci/projects-and-dependencies.md
ci/reporting-and-artifacts.md
ci/test-coverage.md