Testing Without Mocks

on YouTube ↗47m

" summary

Argues that replacing mocks with Nullables — production classes with an encapsulated off switch and a createNull factory — lets tests run the exact same code as production while stubbing only third‑party calls. Shows a homepage controller tested with a nulled Route13 client and nulled HTTP client, demos passing tests that run ~50 ms, keeps just three or four smoke tests, and claims faster, deterministic, refactor‑friendly suites at the cost of adding a createNull factory to IO classes.

AI-written summary · about

" chapters (6)

1. 0:00Testing without mocks
2. 2:33Problems with traditional tests
3. 9:22Nullables pattern
4. 16:29Live coding demo
5. 36:13Refactoring tests
6. 45:43Conclusion

" related talks

• 31mBeyond the Mockery- Why We Should Embrace Testing Without Mocking FrameworksAsh Davies · droidcon New York 2023
• 25mFakes over Mocks: Shift your paradigm and identify monolithic codeCaleb Donoho · droidcon New York 2022
• 29m"Testing. Why so serious?"Viacheslav Shvetsov · RubyC 2017
• 27mReal World Mocking in SwiftVeronica Ray · try! Swift Tokyo 2016
• 41mMocks vs Fakes vs StubsMateusz Herych · GDG DevFest Sofia 2019
• 45mStop Using Mocks (for a while)Harry Percival · PyCon US 2020
• 37mBeyond the Mockery: Why We Should Embrace Testing Without Mocking FrameworksAsh Davies · droidcon Berlin 2023
• 36mTo Mock or Not to MockJustin Searls · Rocky Mountain Ruby 2012