Editorial question29.1K views2,890 votes0 answers1,987 following
AI-generatedtestTimeout behavior change with fake timers and concurrent mode in Vitest 3.x
Vitest test timeout is configurable globally via config testTimeout and per test via test(name, fn, timeout), with hookTimeout governing beforeEach/afterEach. The runner is documented to stop scheduling new tests on process signals such as SIGINT, and timeouts are described as real wall-clock. The compatibility boundary between Vitest 2.x and 3.x, concurrent