Jasmine Spies: Isolate Dependencies and Verify Behavior in Unit Tests
Learn how Jasmine spies isolate external dependencies, verify interactions, and avoid common pitfalls like brittle internal-method spying and state leakage.
Loading…
ReadMeFeed / Community knowledge
#test-doubles
Real questions. Useful conversations. Find the people who know your stack.
javascript
jasmineUsing Jasmine Spies to Decouple Unit Tests from Dependencies
Learn how to use Jasmine spies (spyOn and jasmine.createSpy) to isolate units from dependencies, with a worked example, trade‑offs, and verification steps.
Isolating Side Effects in Jasmine: Spies and the Fake Clock
Learn how to use Jasmine spies and the fake clock to eliminate flakiness in unit tests by isolating HTTP calls, timers, and external dependencies.
Isolating Dependencies in Jasmine: Using Spies to Avoid Real Network Calls
Learn how to use Jasmine spies to isolate units under test, mock HTTP dependencies, and verify function calls without relying on live network requests.
RSpec message expectations and verify-after-execution behavior
RSpec provides distinct mechanisms for verifying method calls on test doubles, specifically through traditional message expectations and the use of spies. While expect().to receive() sets a requirement before the action occurs, spies enable an "act first, assert later" pattern using have_received() . There is a design consideration regarding the internal sta
rspec