The production build registers a service worker whose v1.18.6 data branch serves allowlisted GET /api/* reads network-first. A worker-originated fetch is not subject to Playwright's page.route interception, so the worker re-fetched the real (empty) backend and bypassed every per-spec route.fulfill — a just-created row never surfaced and read-after-write assertions failed. Block the worker in the test context so the route mocks are authoritative; the shipped offline cache is untouched for real users. Separately, the dashboard now batches chart series into /api/measurements/series-batch, a sub-path the **/api/measurements* glob does not match, so it fell through to the empty backend and each chart painted an empty preloaded slice; stub the endpoint with the same populated set.
e2e/
End-to-end browser tests. Playwright 1.60 drives a production build of the app against a real PostgreSQL, with @axe-core/playwright for accessibility assertions. This is the heaviest test tier; CI runs it on every PR, and locally it is worth running when a change touches a UI flow.
Running
pnpm e2e
The Playwright config (../playwright.config.ts) builds the app (next build) and brings up Postgres before the specs run; setup/global-setup.ts seeds the auth + fixture state. The suite is not part of the fast local gate (typecheck / lint / test) — it surfaces at PR CI, so expect responsive/wizard/nav reworks to flag here first.
Layout
setup/—global-setup.ts(auth + DB seeding),test-helpers.ts(shared login + navigation helpers).utils/— fixtures such asmock-dashboard-snapshot.ts.*.spec.ts— one spec per flow: auth/login/redirect, dashboard, charts, the medication-wizard cadences (medications-wizard-*), insights generation + scroll restoration, doctor report, settings, mobile-viewport consistency, locale switch, accessibility (a11y.spec.ts), and thev1427-*regression set.
Convention
Assert against stable data-* attributes (data-slot, data-display-step, root display attrs), not viewport-dependent visible text. Responsive sm:hidden UI changes break getByText on desktop while the underlying element is still present — anchoring on data attributes keeps the specs stable across breakpoints. See ../CLAUDE.md.