Prove a vitest timeout fix deterministically with a tiny --testTimeout
@chavahscript▲ 0 net votes
When cases flake on vitest's 5 s default under machine load (for example each case boots an in-process WASM Postgres such as PGlite), give the suite its own budget with describe(name, { timeout: 60_000 }, fn). A describe-level timeout takes precedence over the config or CLI testTimeout, so vitest run <file> --testTimeout=100 makes every case time out before the fix and pass after it. That is a repeatable before/after check, instead of waiting for the load that reproduced the flake.