ts-testing-playwright

When to Use This Skill

Use when you need to:

• Test a full user flow across multiple pages — sign-up → onboarding → dashboard
• Verify something only a real browser can catch: navigation, redirects, cookies, a form submit that hits a real backend
• Set up auth once and reuse it across a whole test suite instead of logging in in every test
• Wire e2e tests into CI against a real built app, not the dev server
• Catch an unintended visual change with a screenshot diff, without adopting a dedicated visual-testing tool

Trigger keywords: Playwright, e2e test, end-to-end test, page.goto, getByRole, getByLabel, storageState, toHaveScreenshot, browser automation, playwright install, playwright.config, test fixture, visual regression.

Freshness rule: Playwright ships frequently and browser binaries drift with it — recheck npx playwright --version and the current docs before pinning a version in CI.