Mocking Framworks considered, harmful?!

on YouTube ↗01h 18m

" summary

Argues that configurable mock DSLs like GoogleMock macro DSL create fragile, hard-to-refactor tests because C++ lacks standard reflection and frameworks rely on macro trickery; demonstrates concrete alternatives: using Mockator refactoring in Cevelop to extract interfaces or template seams, linker/preprocessor as last resorts, and a plain C++ trace-string mock that the IDE generates to record call sequences. Shows that generated plain code compiles and debugs far more easily than macro magic, and warns against mocking not-yet-written components that prematurely fix stateful APIs.

AI-written summary · about

" chapters (18)

1. 0:00Introduction
2. 2:06Mocking frameworks
3. 3:29Mocks arent stops
4. 5:40The Order
5. 8:14Phase Tests
6. 10:52When should I test
7. 15:28Testable
8. 18:51Configurable tests
9. 22:15Dependency injection
10. 25:36Gene Mauch
11. 27:00Michael Feathers
12. 34:20compiled
13. 35:32assert
14. 38:26macros
15. 40:06plain code
16. 44:16refactoring
17. 50:51walking
18. 57:09design limitations

" related talks

• 01h 01m“Mocking Frameworks considered harmful”Peter Sommerlad · CppCon 2017
• 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
• 06mMocking C++Peter Bindels · Meeting C++ 2016
• 52mPlease don’t mock meJustin Searls · Assert(js) 2018
• 39mPlease Don't Mock MeJustin Searls · JSConf US 2018
• 53mC++ Unit testing - the good, the bad & the uglyDror Helper · NDC TechTown 2018
• 27mReal World Mocking in SwiftVeronica Ray · try! Swift Tokyo 2016