How to Mock in the 21st Century
summary
Presents a concrete recipe for mocking hardware-heavy embedded code by defining a strict replacement layer so MCU drivers can talk either to hardware-in-the-loop or to small debug-adapter–connected simulators. Describes wiring those simulators into an integration-server test harness, reusing existing prototype ports and adapters to run deterministic tests that catch timing bugs and register-state failures missed by unit tests, with working examples on prototype boards and CI integration.
AI-written summary · about
chapters (6)
- 0:00Modern mocking
- 5:58Target and client
- 10:01Speed in testing
- 12:04Hardware testing
- 16:20Evaluating changes
- 19:19Conclusion
related talks
37mBeyond the Mockery: Why We Should Embrace Testing Without Mocking Frameworks
25mFakes over Mocks: Shift your paradigm and identify monolithic code
31mBeyond the Mockery- Why We Should Embrace Testing Without Mocking Frameworks
16mMastering Mocking in Playwright: Simplify API Test Automation
27mReal World Mocking in Swift
01h 01m“Mocking Frameworks considered harmful”
01h 00mTestability and API Design
52mPlease don’t mock me
