Playwright Ci Caching

What it does

This skill significantly speeds up Playwright E2E testing in CI/CD pipelines by caching browser downloads and test artifacts. It avoids repeatedly downloading large browser binaries (approximately 400MB) on each build, reducing setup time from 1-2 minutes. The cache is automatically invalidated whenever the Playwright version changes, ensuring you always use compatible browsers.

When to use it

• You're setting up CI/CD for a project using Playwright E2E tests.
• Your build times are slow due to browser download overhead.
• You want automatic cache invalidation when the Playwright version is updated.
• You’re using GitHub Actions or Azure DevOps pipelines.

Key capabilities

• Caches Playwright browsers based on operating system (Linux, macOS, Windows).
• Extracts the Playwright version from Directory.Packages.props to use as a cache key.
• Automatically invalidates the browser cache when the Playwright version changes.
• Provides example configurations for GitHub Actions and Azure DevOps pipelines.

Example prompts

• "Configure caching for my Playwright tests in GitHub Actions."
• "How can I speed up my Azure DevOps builds with Playwright?"
• "Set up browser caching for Playwright E2E testing."

Tips & gotchas

• This skill requires a Directory.Packages.props file to determine the Playwright version.
• The cache paths are OS-specific: ~/.cache/ms-playwright (Linux), ~/Library/Caches/ms-playwright (macOS), and %USERPROFILE%\AppData\Local\ms-playwright (Windows).
• Ensure your CI/CD pipeline environment has the necessary permissions to write to the cache directory.