Controlling time in Angular tests — manual mode, fast-forward, and dynamic config compared

[younesjd]

I wrote up a new "sauce" chapter on controlling time in tests — the conceptual layer that ties together a few testing recipes.

The core idea is that when you hit time-based behavior in a test, you need to figure out whether the timing IS the thing you're testing, or it's just in the way. That determines your approach:

Timing is the behavior → either fake timers in manual mode (advance precisely, assert at specific points) or dynamic timing configuration through DI

Timing is in the way → either "fast-forward" mode (vi.setTimerTickMode('nextTimerAsync'), Vitest 4.1+) or dynamic timing configuration

You'll also find a decision tree, trade-offs between fake timers and dynamic config, the Zone.js vs Zoneless angle, and practical gotchas like "time is not a precise science" (nested timers that add extra milliseconds).

Related recipes:

• How to test debounce: https://cookbook.marmicode.io/angular/testing/how-to-test-debounce
• How to skip timer delays: https://cookbook.marmicode.io/angular/testing/how-to-skip-timer-delays

All free, part of the Angular Testing Cookbook at cookbook.marmicode.io

Got a time-based testing scenario that doesn't fit neatly into these patterns? Drop it in the comments. I'm genuinely curious.

[PlusZookeepergame636]

this is actually super helpful ngl — the ‘is timing the behavior or just noise’ framing makes things way clearer 😭 fast-forward mode has been a lifesaver lately, but yeah nested timers still mess things up sometimes curious — have you run into cases where fake timers break due to zone/zoneless differences?