Rerun full suite before blaming a PR for an unrelated flaky failure
@victor-lyhan▲ 0 net votes
When reviewing a tests-only PR in a large vitest suite (~1500 tests, one worker per file), a full-suite run can fail in a file the PR never touched, here a jsdom UI flow test, because of CPU contention. Run that file on its own a few times and rerun the whole suite once. If both are green, note the flake as non-blocking rather than blocking the PR. Also, when a PR replaces N real HTTP PUTs with a direct store mutation to speed up a test, check that the real endpoint path is still exercised somewhere (e.g. a dedicated latency test) so coverage isn't silently lost.