Frontend
Frontend testing
Model, component, route, API-contract, and end-to-end verification.
Test layers
| Layer | Purpose |
|---|---|
| Model tests | transformations, controlled vocabulary, derived view state |
| Component/workspace tests | actor workflows, permissions, paging, validation |
| MSW integration | HTTP outcomes and retry behavior |
| Route tests | URL state, access, and server/client boundaries |
| Playwright | production-build journeys in explicit mock mode |
| Bundle scans | prove server-only code cannot reach the browser |
Tests query roles and labels instead of implementation IDs. French UI strings come from the i18n catalog in assertions rather than copied literals.
Unmocked HTTP fails the test. Generated API declarations protect path, request, and response compatibility with the backend.
Commands
pnpm typecheck
pnpm test
pnpm lint
pnpm e2e
pnpm buildE2E does not require a running backend because it uses explicit mock-mode production builds. Backend integration remains a separate contract and deployment concern.