How to NOT waste time
summary
Argues that wasted tester time comes from unclear value and poor testability, so teams do risk analysis, create a test strategy and map product risks; moves work down the stack by preferring API-level tests over brittle GUI checks; gives a concrete story where discussing scope cut regression from three to one week; recommends ensemble testing, checklists, daily runs of automation, better environments and bug reports, and deleting unused artifacts to reclaim hours.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 0:44Know what matters
- 2:12Plan your testing
- 3:40Test smarter not harder
- 5:26Avoid over-engineering
- 6:50Learn from feedback
- 8:14Use heuristics and checklists
- 9:38Stop mindless test cases
- 10:43Optimize environments
- 11:46Cut unnecessary work
- 12:50Automate wisely
- 13:33Fix bad meetings
- 14:19Summary and resources
related talks
34mesting in modern times: A story about quality and value
01h 00mWhy Software Testing Is a Waste of Time
28mYour Testing Strategy is broken - lets fix it!
34mHelping Testers Add Value to Agile Projects
10mThe value of testing
22mTest Effective Development
41mExits on the (QA) Highway to Hell
51mRedefining test automation