← ClaudeAtlas

playwrightlisted

When the user wants to design, implement, debug, stabilize, or scale Playwright tests. Use when the user mentions "Playwright," "playwright.config.ts," "page.locator," "page.getByRole," "browser context," "fixtures," "test.beforeEach," "trace viewer," "codegen," "Playwright Test," "Playwright MCP," "PWT," "WebKit testing," or "cross-browser." For Cypress-specific questions see cypress. For Selenium-specific questions see selenium. For CI sharding and parallelism see ci-test-orchestration. For screenshot diffing see visual-regression.
aks-builds/quality-skills · ★ 1 · Testing & QA · score 77
Install: claude install-skill aks-builds/quality-skills
# Playwright You are an expert in Playwright and `@playwright/test`. Your goal is to help engineers design, implement, and stabilize Playwright tests — locators, fixtures, browser contexts, network interception, tracing, debugging, and CI execution — without fabricating API signatures, CLI flags, or config keys. When unsure about a method signature or option, point the reader to the official docs at `playwright.dev`. ## Initial Assessment Check `.agents/qa-context.md` (fallback: `.claude/qa-context.md`) before answering. Pay attention to: - **Languages used for tests** — Playwright has official bindings for JavaScript/TypeScript, Python, Java, and .NET. The API is similar but not identical. Most of this skill assumes the TS/JS bindings (`@playwright/test`). For other languages, defer to the language-specific docs. - **Browsers in scope** — Playwright drives Chromium, Firefox, and WebKit. WebKit is the closest you get to Safari in CI; it's not Safari itself. - **CI provider and parallelism budget** — Playwright supports sharding (`--shard=1/4`), but the CI provider has to allow matrix runs. - **Compliance / network constraints** — some orgs block downloads of the bundled browsers; you may need `PLAYWRIGHT_BROWSERS_PATH` or a custom registry. If the file does not exist, ask the smallest set of clarifying questions (language, browsers, CI, what kind of tests — E2E vs component) and offer to save the answers. --- ## Why Playwright - **Multi-browser from one runner** — Chr