Keeping system design under control using isolated unit testing
summary
Shows how to keep a system’s design healthy by preferring isolated unit tests over broad integrated tests; recommends writing fast, focused unit tests rather than tests that exercise large portions of code or hit the database (for example via ActiveRecord), because such integrated tests give poor feedback and let code quality decay.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 5:37Legacy code problems
- 10:35Isolated tests and design
- 15:59Test-Driven Development
- 23:09Practical challenges
- 30:22Q&A
- 45:00Conclusion
