Stop Using Mocks (for a while)

on YouTube ↗45m

" summary

The claim is blunt: stop using mocks for a while and instead build an adapter, inject it, and use a small in‑memory fake or integration tests. Concrete tools: an adapter class that hides requests, a fake cargo API backed by a dict, dependency injection instead of mock.patch, sandbox or a local fake container, and VCR.py for recordings. Before this change a feature spawns ~12 tests with 5–6 mocks each; after it yields Functional Core, Imperative Shell, clearer tests, Dependency Injection and hand-rolled fakes that actually work and reduce brittleness.

AI-written summary · about

" chapters (10)

1. 0:00Introduction
2. 0:57The Heros Journey
3. 4:11Example Code
4. 8:40Sync to API
5. 12:25Mocks are Broken
6. 16:56Adapter Example
7. 22:10Build a Fake
8. 27:08Dependency Injection
9. 33:32Wrapping Up
10. 37:25Building a Fake API

" related talks

• 25mFakes over Mocks: Shift your paradigm and identify monolithic codeCaleb Donoho · droidcon New York 2022
• 52mPlease don’t mock meJustin Searls · Assert(js) 2018
• 37mBeyond the Mockery: Why We Should Embrace Testing Without Mocking FrameworksAsh Davies · droidcon Berlin 2023
• 31mBeyond the Mockery- Why We Should Embrace Testing Without Mocking FrameworksAsh Davies · droidcon New York 2023
• 39mIntro to Mocking: Why Unit Testing Doesn't Have To Be So HardDaniel Davis · DjangoCon US 2015
• 49mFor those about to Mock I salute you!Jason Myers · PyOhio 2016
• 27mDe-mock your testsJarosław Michalik · droidcon Berlin 2022
• 33mMock Me If You Can: Using Mocks in Container Applications for Integration TestingJohn Coyne · Open Source Summit North America 2025