“Mocking Frameworks considered harmful”

on YouTube ↗01h 01m

" summary

Argues that common C++ mocking frameworks (GoogleMock, Trompeloeil) introduce macro-heavy DSLs, late runtime verification on object destruction, and fragile white-box tests that over-specify call sequences and increase coupling. Shows practical alternatives: refactor to template seams or extracted interfaces, use IDE refactorings and linker/preprocessor seams, or generate plain C++ call traces with Mockator in Cevelop. Notes quirks like ON_CALL warnings driving overuse of EXPECT_CALL and demonstrates the generated stubs and traces work and give clearer failures.

AI-written summary · about

" chapters (9)

1. 0:00Introduction to mocking frameworks
2. 1:47What is mocking and why use it
3. 10:29When to use test doubles
4. 17:40Introducing seams for testability
5. 24:53Mocking frameworks in C++
6. 35:00Problems with mocking frameworks
7. 41:46History and limitations of mocking
8. 47:42Dangers of over-mocking
9. 51:17Q&A session

" related talks

• 01h 18mMocking Framworks considered, harmful?!Peter Sommerlad · ACCU 2018
• 06mMocking C++Peter Bindels · Meeting C++ 2016
• 53mUsing Trompeloeil - a mocking framework for modern C++Björn Fahller · NDC Oslo 2017
• 31mBeyond the Mockery- Why We Should Embrace Testing Without Mocking FrameworksAsh Davies · droidcon New York 2023
• 01h 25mUsing Trompeloeil, a mocking framework for modern C++Björn Fahller · ACCU 2017
• 37mBeyond the Mockery: Why We Should Embrace Testing Without Mocking FrameworksAsh Davies · droidcon Berlin 2023
• 52mPlease don’t mock meJustin Searls · Assert(js) 2018
• 59mC++ Unit testing - the good, the bad & the uglyDror Helper · NDC Oslo 2017