ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
When using Jest's modern fake‑timer implementation (jest.useFakeTimers({ modern: true })) and advancing time with jest.advanceTimersByTime, microtasks created by Promise.resolve().then or async/await are not automatically flushed. This leaves pending promises unresolved, causing tests that await those promises to hang unless jest.runOnlyPendingTimers (or jes
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
Goal: Verify that date‑conversion logic behaves identically when Vitest’s fake timers are used across different developer machines and CI runners. Constraint: vi.useFakeTimers() and vi.setSystemTime() shift the mocked clock but leave the process timezone unchanged; the effective zone is determined by the TZ environment variable that must be set before the Vi
Jasmine fake timers and Node.js DNS lookup callback timing The goal is to write a unit test that exercises DNS‑resolution logic while using Jasmine’s fake‑timer utility to make all asynchronous callbacks fire synchronously, enabling deterministic, fast test execution. However, Jasmine’s jasmine.clock() only replaces JavaScript‑based timers (setTimeout, setIn
jest
nodejs