Become a Test Whisperer: what are your tests are telling you?
summary
Examples name the problem and the fix: controller abstractions created with macro-driven controllers force every test through HTTP scaffolding so splitting out a service layer makes tests simpler; noisy logs get hidden by capture_log so assert the expected log instead of swallowing failures; race conditions show up as RabbitMQ duplicate messages and get fixed with a database lock or single listener; tests are diagnostic tools that reveal architectural smells when they fail or lie.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:17Testing is hard
- 2:05What is a Whisperer
- 4:25Smell vs Code
- 4:41Start over
- 5:05Why do we test
- 8:59First example
- 12:44Macros
- 21:04Existing code
- 25:52Conclusion
related talks
57mAdvanced Testing Techniques: Tips from the trenches
01h 05mMicrotesting
37mClean Test Code
21mTests That Help you Find Defects Faster
46mBetter code through boring(er) tests
53mThe secret unit testing tools no one ever told you about
29mEffective tests and testing effectively
31mGoing on a Testing Anti-Pattern Safari