Please Don't Mock Me

on YouTube ↗39m

" summary

Argues that popularity of a mocking library doesn’t matter and that after a decade of TDD with mocks most people use them poorly; uses test double/testable to show specific abuses (partial mocks, half-mocked stacks, mocking weird third-party APIs) and prescribes concrete fixes: wrap third-party libs, fake whole dependencies, prefer real values. Demonstrates a working discovery testing workflow that builds a keynote from notes via a sentiment analyzer and slide generator, proving the approach with small passing tests and test double examples rather than abstract advice about mocking libraries.

AI-written summary · about

" chapters (12)

1. 0:00Start
2. 2:20Dependency
3. 11:54Mocking out 3rd-party code
4. 15:24Tangling logic and delegation
5. 20:08Mocking dependencies halfway down the stack
6. 20:21Expense System
7. 22:32Mocking in tests of existing code
8. 24:06Mock dependencies, but pass real values
9. 25:19Enabling highly- layered designs
10. 27:02Make small things
11. 31:42Growing Object Oriented Software Guided by Tests
12. 36:38Intention-revealing names Discoverable organization

" related talks

• 52mPlease don’t mock meJustin Searls · Assert(js) 2018
• 36mTo Mock or Not to MockJustin Searls · Rocky Mountain Ruby 2012
• 31mBeyond the Mockery- Why We Should Embrace Testing Without Mocking FrameworksAsh Davies · droidcon New York 2023
• 47mYay! Mocks!Corey Haines · Aloha RubyConf 2012
• 37mBeyond the Mockery: Why We Should Embrace Testing Without Mocking FrameworksAsh Davies · droidcon Berlin 2023
• 01h 01m“Mocking Frameworks considered harmful”Peter Sommerlad · CppCon 2017
• 30mMocks, Stubs, and Spies, Oh MyBrian Gardner · droidCon NYC 2018
• 29m"Testing. Why so serious?"Viacheslav Shvetsov · RubyC 2017