E2E Testing (Playwright)

Automates real user journeys in a real browser. Complements playwright-cli (tool mechanics) by deciding WHAT to test and HOW to write tests that don't rot.

What to cover (in priority order)

1. Money & identity paths: signup, login, logout, password reset, checkout/payment.
2. Core CRUD journeys: create → read → update → delete of the app's main entity.
3. Critical business rules: permissions (user A cannot see user B's data), limits, validation.
4. High-traffic pages: they load, render real data, no console errors.

Do NOT e2e-test what a unit test covers better (pure logic, formatting, calculations) — e2e is slow; keep the suite small and meaningful.

Setup