test(e2e): give every switching journey its own session row

The suite only passed on one worker: four specs shared the scope
delegate's cookie jar and moved the same session's record selector, so
at CI's two workers they moved the epoch under each other and the
failures were the harness racing itself.

- one login per switching spec, which is a separate session row and
  therefore a separate selector; the login bucket is cleared between
  them because the ceiling is five and setup now signs in eight times
- each such spec runs in exactly one project, since a second project
  drives the same row from two browsers
- clear what the browser suite WRITES, so it can be run twice: the
  write journey saves a minute-rounded reading and collided with itself
- wait for adoption after leaving a record, retry a lost switch the way
  a person would, and budget the cross-tab hold for machine load
This commit is contained in:
Marc-André Bombeck committed 2026-08-06 23:04:08 +02:00
1 parent 9c99ec34d6
commit 6e5b420e4e
7 files changed
+440 -97

No files matched your search

+11 -6
View File
@@ -117,13 +117,18 @@ export default defineConfig({
testIgnore: [
"v137-sharing-managed-profiles.spec.ts",
"v137-sharing-managed-profiles-a11y.spec.ts",
// v1.37.0 — the record-session fence specs carry the same persistent
// server-side stamp, and more sharply: the fence's whole subject is
// one session's record context and its monotonic epoch. Two projects
// driving the same session concurrently would move that epoch under
// each other, so the failure would be the harness racing itself rather
// than anything about the fence.
// v1.37.0 — every spec that MOVES a session's record selector runs in
// exactly one project.
//
// Each of these now has its own login and its own session row (see
// `FENCE_STORAGE_STATE_PATH` in `e2e/setup/global-setup.ts`), which is
// what lets them run beside each other at any worker count. A second
// PROJECT is the one thing a separate jar cannot fix: it would drive
// the very same row from two browsers at once, moving the epoch under
// itself. The scoped-sharing journeys above are excluded for the same
// reason, one release earlier.
"v137-record-session-fence.spec.ts",
"v137-sharing-cross-tab-session.spec.ts",
// Runs only in the service-worker project.
"v137-record-session-fence-offline.spec.ts",
],