The Unit Tests Strike Back: Testing the Hard Parts
summary
Unit testing often breaks down into a plan A that vaporizes and a sequence of pragmatic fallbacks: use mocks or dependency injection, make external services ubiquitous (example zookeeper run locally), gather failure stats like run five thousand times and fail three, or instrument with sanitizers and beef up acceptance tests. For hard legacy cases options include friend classes, changing access or the extreme define private public hack to link against binaries. A half million line Fortran dependency pushes teams toward acceptance testing and sanitizers rather than pure unit tests.
AI-written summary · about
chapters (7)
- 0:00Introduction and context
- 1:04Defining unit test goals
- 2:54The reality of difficult testing
- 8:53Managing flaky tests
- 23:42Dealing with problematic code
- 37:39Plan omega and conclusion
- 41:41Questions and answers
related talks
57mAdvanced Testing Techniques: Tips from the trenches
40mIntegration Testing from the Trenches - Rebooted
44mTesting the untestable - patterns and use cases analysis
01h 01mBack to Basics: Unit Testing in C++
55mThe Science of Unit Tests
37mClean Test Code
19mGet More From Your Unit Tests
01h 19mYou Can't Test This? Hammertime!