playwright

name	playwright
description	Playwright browser/E2E testing workflow for runtime verification. Use when Codex needs to add, run, debug, or document frontend/browser tests, smoke-test a dev server, verify UI flows during athena-runtime-verify, capture traces/screenshots, or turn manual browser checks into repeatable tests.

/playwright — Browser Runtime Tests

Core Rule

Use Playwright when the acceptance signal depends on a real browser: routing, forms, auth flows, rendering, navigation, API-backed UI state, responsive layouts, downloads/uploads, or regressions that unit tests cannot see.

For Athena v9.8.0, this skill is the frontend/E2E test arm of athena-runtime-verify. It should produce evidence that can be pasted into sprints/{slug}/runtime-verify.md under ## 测试场景 (实跑).

Official references:

• Playwright intro: https://playwright.dev/docs/intro
• Writing tests: https://playwright.dev/docs/writing-tests
• CLI: https://playwright.dev/docs/test-cli
• Codegen: https://playwright.dev/docs/codegen
• Trace viewer: https://playwright.dev/docs/trace-viewer

Workflow

1. Detect project setup before adding anything:

   • Existing Playwright: inspect playwright.config.*, tests/, e2e/, package.json scripts.
   • No Playwright: prefer adding @playwright/test and a minimal config/test file that fits the repo.
   • If the repo already uses Cypress/Vitest browser mode/etc., avoid wholesale migration; add Playwright only if runtime verification needs real browser coverage.