test(app): every shell suite drops late replays after a test

The client journey could fail after it passed: since V1-1.6 the client page
reloads its animals after a restore, and that replay outlived the test. One
support helper unroutes without waiting, for the three shell specs. Found by
the V1-1.6 verifier. Memory: BDR-079, LRN-087 to 089.
This commit is contained in:
bchanot committed 2026-10-26 17:38:52 +01:00
1 parent 212392263c
commit 10413478fb
8 files changed
+74 -9

No files matched your search

+5 -3
View File
@@ -33,9 +33,11 @@ object with the service key). Rows around the subject of a test (clients,
animals, relations) are written as postgres by `e2e/support/records.ts`,
every value quoted as an SQL literal. `pnpm db:sandbox down` removes all of it.
`pnpm db:sandbox e2e-shell <args>` passes its arguments to Playwright: one
spec file, `--project`, `--grep`. The animal suite removes its routes after
each test without waiting for them, so an answer still in flight when the last
check passed is dropped with the context instead of failing the test.
spec file, `--project`, `--grep`. Every shell suite removes its routes after
each test without waiting for them (`dropLateReplays`), so an answer still in
flight when the last check passed is dropped with the context instead of
failing the test (the V1-1.6 verifier saw the client journey fail that way once
the client page reloads its animals after a restore).
## 2. Prerequisites