mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-10 13:22:14 +00:00
Marc-André Bombeck
6e5b420e4e
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
26 lines
819 B
TypeScript
26 lines
819 B
TypeScript
/**
|
|
* Re-export pin for the seeded test-user identity. The cookie jar that
|
|
* authenticates each spec is captured ONCE in `global-setup.ts` and the
|
|
* specs reach for it via `STORAGE_STATE_PATH` directly. We keep this
|
|
* file (instead of a barrel inside global-setup) only so future helpers
|
|
* specific to the spec-side (e.g. multi-user scenarios that need
|
|
* fresh logins) have a natural home.
|
|
*/
|
|
export {
|
|
E2E_USER,
|
|
E2E_OWNER,
|
|
E2E_SCOPE_DELEGATE,
|
|
E2E_SCOPE_RECORDS,
|
|
E2E_LEVEL_RECORDS,
|
|
E2E_DELEGATE_MARKER_KG,
|
|
E2E_OWNER_MARKER_KG,
|
|
STORAGE_STATE_PATH,
|
|
OWNER_STORAGE_STATE_PATH,
|
|
DELEGATE_STORAGE_STATE_PATH,
|
|
SCOPE_DELEGATE_STORAGE_STATE_PATH,
|
|
SCOPE_A11Y_STORAGE_STATE_PATH,
|
|
FENCE_STORAGE_STATE_PATH,
|
|
FENCE_OFFLINE_STORAGE_STATE_PATH,
|
|
CROSS_TAB_STORAGE_STATE_PATH,
|
|
} from "./global-setup";
|