Testing + Playwright E2E
When to use
- •Adding or updating unit/integration tests.
- •Running the required CI checks before commit.
- •Designing or debugging Playwright/E2E flows.
Required checks (default workflow)
- •
npm run compile - •
npm run lint - •
npm run test:unit
E2E + visual tests
- •
npm run test:e2eruns Vitest E2E withvitest.e2e.config.ts. - •
npm run test:visualruns Playwright visual tests (playwright-visual.config.ts). - •Set
E2E_BASE_URLif you need a non-default host.
Workflow guidance
- •Prefer small, focused unit tests in
__tests__for components and lib helpers. - •When adding a new user flow, update the E2E narratives so behavior stays aligned.
- •If a test fails due to output changes, update snapshots/fixtures and document why.
References
- •codex/skills/markdowntown-testing/references/tests.md
- •codex/skills/markdowntown-testing/references/playwright.md
Guardrails
- •Keep tests deterministic; avoid time-based flakiness where possible.
- •When documenting QA evidence, use
qa-verification.