How to Stop Hating your Tests
summary
Distills 15 recurring test-suite failures into actionable fixes: avoid combinatorial blowup (rule of product — 2^4 = 16 test cases), split suites into two extremes (maximally integrated vs maximally isolated), prefer small objects with one public method and at most three dependencies, use a given‑when‑then style for clearer failures, measure hits‑per‑line to cut redundant coverage, cap build time, expect super‑linear slowdowns and many false negatives (>90%), and use controlled doubles like testdouble (npm) carefully.
AI-written summary · about
chapters (19)
- 0:00Start
- 0:47How To Stop Hating Your Tests
- 3:55Isolation
- 6:16Unix Terminal
- 6:57The Rule of Product
- 21:02Breaking Up with Your Test Suite
- 21:12The Testing Pyramid
- 26:34Redundant Code Coverage
- 27:44How Do You Detect Redundant Code Coverage
- 28:55Outside in Test-Driven Development
- 29:22Discovery Testing
- 29:44Careless Mocking
- 32:13Application Frameworks
- 34:21Useless Error Messages
- 36:34Slow Feedback Loops
- 37:58Bad Error Messages
- 39:41Painful Test Data
- 41:14Super Linear Build Slow Down
- 43:32False Negatives
