playwright-ci

Automate CI/CD pipeline setup and maintenance for Playwright tests.

1|Updated Jul 5, 2025
One-click install
npx skills add https://github.com/kevinchatham/tressi --skill playwright-ci
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playwright-ci
Source: https://github.com/kevinchatham/tressi/tree/main/.agents/skills/playwright-skill/ci
Command: npx skills add https://github.com/kevinchatham/tressi --skill playwright-ci

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill consolidates production-ready CI/CD configurations for Playwright across major providers, enabling teams to ship reliable tests with consistent patterns for PR validation, multi-project runs, and automated reporting.

Core Features & Use Cases

  • Production-ready CI/CD configurations for Playwright across GitHub Actions, GitLab CI, CircleCI, Azure DevOps, and Jenkins, including parallel execution, reporting, artifact management, and global setup/teardown.
  • Includes reusable workflows, environment secrets handling, containerized runs, and multi-provider templates to accelerate CI adoption.
  • Use cases include PR validations, staging deployments, and nightly regressions with merged and blob reports for quick feedback.

Quick Start

Integrate the included CI workflows into your repository to start using production-grade Playwright CI patterns.

Frequently Asked Questions about playwright-ci

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up parallel execution for Playwright tests in CI/CD?

Parallel execution for Playwright tests is configured using provider-specific workflows that shard tests across multiple machines. This Skill provides templates for GitHub Actions, GitLab CI, CircleCI, Azure DevOps, and Jenkins to automate sharding and merge blob reports for quick feedback.

What's the best way to manage Playwright test artifacts and reports across different CI providers?

Managing Playwright test artifacts and reports across CI providers is handled using standardized patterns for blob reporting and JUnit/HTML outputs. These configurations ensure consistent artifact management and automated reporting for PR validations and nightly regressions.

Does this support containerized Playwright test runs in Jenkins and Azure DevOps?

Yes, containerized Playwright test runs are fully supported across Jenkins and Azure DevOps. The included CI/CD configurations cover containerized environments, environment secrets handling, and global setup/teardown to ensure reliable, scalable test execution.

Can I use reusable workflows for Playwright CI to streamline multi-project runs?

Reusable workflows for Playwright CI are included to streamline multi-project runs and accelerate CI adoption. These templates facilitate multi-provider integration, allowing teams to ship reliable tests with consistent patterns for staging deployments and PR validation.

Why do I need blob reporting for Playwright tests in parallel CI pipelines?

Blob reporting is needed for Playwright tests in parallel CI pipelines because it allows individual test shards to generate separate reports that are later merged. This approach ensures reliable, scalable test runs and provides quick feedback through consolidated HTML and JUnit reports.

What CI/CD templates are available for Playwright global setup and teardown?

CI/CD templates for Playwright global setup and teardown are available across GitHub Actions, GitLab CI, CircleCI, Azure DevOps, and Jenkins. These templates handle environment secrets and ensure consistent state initialization and cleanup for reliable automated test execution.