Marc-André Bombeck
bdfea7dd85
Three properties here cannot be answered by a mocked client, and each has a shape that would pass a weaker assertion while being wrong: - filing a visit against a due checkup twice satisfies it ONCE. Phrased as "the second call returned 200" it proves nothing, so the assertion is that lastSatisfiedAt did not move — and the instant is captured once, because two calls milliseconds apart are two different filings and the forward-only guard correctly advances on the later one. - a lab commit writes one link PER RESULT ROW. A test that asserted "there is a link" would pass on one link for a three-marker panel. - the visit list's condition filter runs in SQL. With one visit in the account a filter and no filter return the same list, so there are always two. The bulk arm gets per-entry tolerance over a hundred documents, one unknown id reported as one failed row with the rest filed, and a foreign visit refusing the whole batch before anything is written. The e2e spec proves the incidental-linking promise once, addressing stable data-slot attributes rather than viewport text: a visit saves with a date and nothing else, and a document dated inside the window offers that visit, pre-selected because there is exactly one, and files itself against it.
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.