dotnet-playwright-ci-cachinglisted

# Caching Playwright Browsers in CI/CD A concise guardrail for caching Playwright browser binaries (~400MB) in CI/CD pipelines to avoid redundant downloads. Targets .NET projects using Central Package Management (CPM) with GitHub Actions or Azure DevOps. **Acronyms**: CI/CD (Continuous Integration/Continuous Delivery), CPM (Central Package Management), E2E (End-to-End). ## When to Use This Skill - Setting up CI/CD pipelines for .NET projects with Playwright end-to-end tests - Reducing build times caused by repeated Playwright browser downloads (~400MB) - Implementing automatic cache invalidation when Playwright package version changes - Configuring GitHub Actions workflows to cache Playwright browser binaries efficiently - Adapting Azure DevOps pipelines to avoid redundant browser installation on every run - Creating cross-platform CI caching that works on Linux, macOS, and Windows runners - Debugging cache misses caused by version mismatch between SDK and cached browsers ## Related Skills | Skill | Scope | When | |-------|-------|------| | `dotnet-playwright-blazor` | Writing Playwright tests for Blazor apps | Creating E2E tests that this caching accelerates | | `dotnet-project-structure` | Central Package Management setup | Defining `Directory.Packages.props` for version extraction | ## Core Principles 1. **Version-Based Cache Keys** — Use the Playwright NuGet version from `Directory.Packages.props` as cache key. Why: automatic invalidation on package upgrade withou