Test Effective Development
summary
Argues that testing must trade off confidence versus efficiency and offers concrete tactics: measure tests by boundaries and action scope, prefer single-action tests to avoid the influencer curse, and use a size-based split — flashlight tests (single-action integrated) for small apps and laser tests (single-action isolated) for large ones. Recommends switching strategies when integrated tests exceed 500 lines of code. Claims these tactics reduce production bugs and cut wasted time; reports applying them with clients improves confidence and test efficiency.
AI-written summary · about
chapters (16)
- 0:00Intro
- 8:55Confidence and Efficiency
- 14:37Choosing the right combination
- 15:09Confidence score
- 15:21Efficiency
- 16:06Influence
- 16:16Conclusion
- 16:31Isolated vs Integrated
- 16:58Size
- 17:29Confidence
- 18:03Efficient
- 18:34Integrated Tests
- 19:27New Test Types
- 19:53Flashlight Test
- 20:48When to switch
- 21:06Summary
related talks
27mTest Effective Development - End 2 (What) End?
48mTesting is Confidence - A Developer's Perspective
11mNeed For Tests: Most Wanted
57mAdvanced Testing Techniques: Tips from the trenches
29mTesting Applications - How to Do It Better?
42mIntroducing the benefits of the testing diamond
49mESSENTIALS - Canon Test-Driven Development
42mEffective Developer Testing: taking it to the next level