playwright-ci

Test sharding splits Playwright test files across multiple GitHub Actions runners to reduce wall-clock time. This Skill provides pipeline templates that configure parallel execution and merge sharded blob reports into a unified, actionable artifact for fast triage.

Merging Playwright reports from sharded CI runs requires selecting compatible blob reporters to collect artifacts from all shards. This Skill configures your CI pipeline to capture, merge, and present unified HTML reports and traces for fast triage when tests fail.

Caching Playwright browser binaries in a Docker CI pipeline involves configuring consistent caching paths within your containerized runs. This Skill provides production-ready configurations that standardize browser dependency installation and caching to speed up pipelines and ensure stability.

Yes, this Playwright CI configuration supports global setup and teardown for authentication. It wires environment preparation patterns to ensure storageState and artifacts remain consistent, handling one-time setup tasks like authenticated sessions reliably across CI providers.

Sporadic Playwright CI failures often stem from environment instability, requiring retries only in CI and trace-on-retry behavior. This Skill applies production reliability guardrails to standardize retry configurations and capture traces exclusively for failed attempts, improving debuggability.

Yes, you can use GitLab CI for containerized Playwright test execution. This Skill provides copy-paste workflow templates for major CI systems including GitLab CI, supporting containerized runs, parallel sharding, and artifact reporting across different providers.