The Lazy Tester
summary
A tester reframes “lazy” as trimming boring work: a Chromium bug turns out to reproduce across OSes so adding Linux-specific regression was unnecessary; a project has 20 interlaced teams and tight deadlines that force rushed testing; repetitive installer checks get replaced with bash scripts that automate uninstall/update cycles and save hours per release; diagnosis of executive dysfunction explains why some people struggle with repetitive tests; use retrospectives and targeted automation to buy time for high-value exploratory work.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:53Story
- 10:34Boredom
- 11:50Mental Health
- 16:12The Pitfalls
- 21:25How much testing is too much
- 23:54The environment
- 26:09retrospectives
- 28:18final message
- 30:07QA
related talks
12mThe Lazy Tester: Musings On Being Efficient
45mSerendipity and Perseverance — Injecting Testing in a Test-Resistant Team
26mKeeping Your Tests Lean
39mThe Good Testing, The Bad Testing and The Ugly Testing
43mRegression Obsession
45mBuilding Tools to Free up Exploratory Testers
51mRedefining test automation
47mDevelopers Are (Not) Lazy! Why is It So Difficult to Get Programmers to Do Unit Testing