Marc-André Bombeck
d3d32ff8e0
The mobile project read the day as final on a table with no sleep in it. The rows were gone; what was left was the dashboard snapshot the desktop run built from them. It carries the sleep-freshness the digest reads, it lives in the analytics SWR bucket at sixty seconds fresh and an hour of stale-serve, and a DELETE straight into Postgres does not touch it. So the second project asked whether last night's sleep was in, and a cached answer from the first project said yes. The purge now goes through the bulk-delete route. That tombstones the rows the way the management list does, recomputes the rollup buckets the snapshot reads through, and hard-evicts the bucket, so the next read rebuilds from the table rather than from the run before it. The delete-by-external-id route names the rows the way this spec does, but it invalidates without evicting, and a marked-stale cell is served while it revalidates - the next read would still have been the stale one. The ids come from SQL because the measurements list collapses overlapping sources to one row per day and can hide a row that still counts. The purge stays where it is rather than moving into the cleanup block: the eviction only happens when the delete removes something, so tidying up at the end of each run would leave the next one with nothing to delete and the same stale snapshot. The starting state is asserted, not assumed, and it stays that way.
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/—test.ts(the suite'stest+expectentry point),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.
Conventions
Import test and expect from ./setup/test, never from @playwright/test — types (Page, Route, …) still come from the package. The entry point extends Playwright's test with an automatic fixture that drops route handlers and page listeners after every test, so a handler left in flight cannot fail the test it belonged to once the context closes. src/__tests__/e2e-route-cleanup-guard.test.ts enforces the import boundary.
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.