ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #jasmine
When testing async JavaScript with Jasmine, decide between done(), promise returns, or async/await. This guide compares patterns, explains trade‑offs, and shows concrete test examples for setTimeout, fetch, and custom promises.
Learn how to use Jasmine spies (spyOn and jasmine.createSpy) to isolate units from dependencies, with a worked example, trade‑offs, and verification steps.
Jasmine's built-in mock clock lets you test debounce, expiry, and polling logic deterministically — no real waiting, no flaky CI. Here's how install(), tick(), and mockDate() work, plus the uninstall and microtask pitfalls.
Learn how to use Jasmine spies and the fake clock to eliminate flakiness in unit tests by isolating HTTP calls, timers, and external dependencies.
Jasmine's spyOn replaces one method on one object, records its calls, and restores the original after each spec. Here's how to pick the right strategy and avoid the common traps.
Learn how Jasmine’s native spies let you replace collaborators, track calls, and stub behaviour without adding a mocking library, plus pitfalls to avoid.
A step‑by‑step guide to identify why a Jasmine spec that uses setTimeout, Promise, or AJAX hangs or times out, and how to fix the done() callback usage.
A decision guide for Jasmine timer tests: when to use jasmine.clock() for deterministic, instant specs versus real timers, with a concrete install/tick/uninstall example and a validation spec.
Jasmine spies let you stub dependencies and verify interactions without real implementations — but overusing toHaveBeenCalledWith makes tests brittle. Here's how to spy well.
javascript