Marc-André Bombeck
c39bf0d0ed
The dashboard assertion called itself "the assertion that they cannot drift apart silently" and then pinned 50. They have already drifted. The tile's denominator is the day's expected slots, which a deliberate skip does not leave, and its numerator counts only rows carrying a `takenAt` (`src/lib/analytics/schedule-anchored-compliance.ts:141-164`). The card's engine — `src/lib/analytics/compliance.ts`, the documented single source of the percentage — drops a skip from the denominator outright (`src/lib/analytics/compliance/ledger.ts:43-47`), which the counts nine lines earlier already assert. One afternoon, two answers. The note now says that, names which engine is authoritative, and the number stays pinned as what the server's daily buckets really produce rather than as agreement. The refusal flow was named for a schedule that does not exist and proved something else: the 404 comes from the ownership guard, before the body is read and before any schedule code runs. `expect(refused.data).toBeNull()` proved nothing either — the error envelope always carries a null `data`. So the test is renamed for what it does prove, the empty assertion is dropped, and the case the old title promised is added: a pin onto an instant that is not one of the medication's slots, refused with the documented 422.
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.