Testing a debounced input without waiting out the real delay

My debounced search box waits 400ms before it fires. Testing it for real means every run of the suite sits there waiting.

IntermediateRead 6 minDoing: about 45 minutes7 steps

▶ Start

What you'll have at the end

The debounce test passing in milliseconds, using fake timers instead of a real wait

Before you start

You need

A component test file that already renders a debounced input with Testing Library, where the component's own effect calls setTimeout once per change, clears it in its cleanup function, and calls an async function once the delay passes.

Not covered

A throttled handler that fires repeatedly at a fixed rate while the user keeps typing, instead of once after they stop; that needs a running call count checked at each interval, not one trailing assertion.

Leans on

7 steps

Where to go next

Swap fireEvent for user-event in tests

when the interaction itself, not the timing around it, is what the test needs to get right

One slow test in the suite is still hitting the real network

when the slow, flaky call is a real network request rather than a debounce timer

Checked 25 Aug 2026

Part of the Vitest Testing Framework cookbook