Did It Actually Send?
Part 4 of Getting Started with Mocks: the notifier stops returning a message and starts sending one, so the test needs a spy instead of a return value.
Posts about getting started with mocks
Browse 9 posts in this category
Make Failure Boring with Mocks
Part 3 of Getting Started with Mocks: the same seam, now returning refusals, timeouts and nonsense, so the failure paths finally get tested.
Mock the Wire
Part 7 of Getting Started with Mocks: a fake HTTP server finally runs the real client, so paths, headers, and parsing get tested. Java, Node, Go, Python.
Test Behavior, Not Choreography
Part 5 of Getting Started with Mocks: a test that pinned the retry schedule broke on a change no customer could notice. Here is how to rewrite it.
They Aren't All Mocks
Part 6 of Getting Started with Mocks: stub, spy, fake, mock, and dummy, sorted by what each one does. Java, Node, Go, Python.
What Mocks Are Actually For
Part 1 of Getting Started with Mocks: the one job a mock does, the five situations where you need one, and what a green mocked test does not prove.
When Handwritten Mocks Stop Scaling
Part 9 of Getting Started with Mocks: a decision framework for stubs, fakes, fake servers, mock servers, record-and-replay, and real dependencies.
Your First Useful Mock
Part 2 of Getting Started with Mocks: a test you cannot write, one seam, and the smallest mock that makes a delayed package happen. Java, Node, Go, Python.
Your Mock Is Lying
Part 8 of Getting Started with Mocks: the carrier renames a field, production breaks, and every mocked test still passes. Java, Node, Go, Python.