Your Testing Strategy is broken - lets fix it!
summary
Argues that test quantity is a bad proxy and claims 100% coverage gives false confidence, pushing instead for example mapping and behavior-driven development to turn requirements into shared, testable scenarios; recommends decision tables, equivalence partitioning and boundary value analysis, and tools like Cucumber for collaboration; prioritizes integration points and risky flows over trivial unit checks, even giving permission to delete pointless tests — practical homework: model one behavior before coding and remove one test that adds no risk reduction.
AI-written summary · about
chapters (10)
- 0:00Meet Luise
- 1:11Rethinking Testing
- 5:47Broken Testing Habits
- 10:35Real-World Testing
- 13:39Challenging Testing Pyramids
- 16:01Risk-Driven Testing
- 18:57Communication Tools
- 24:40Culture and Blame
- 25:47Practical Fixes
- 27:12Final Thoughts
