The Lazy Tester: Musings On Being Efficient
summary
Reframes "lazy" as deliberate efficiency and gives two concrete shifts: make testing a shared responsibility with risk-based guidance so QA stops bearing every go/no-go decision, and replace a monolithic 4–8 hour overnight regression with test-as-a-service and multiple runs for multiple duns — smaller, centralized suites organized like engineering code so engineers run fast regressions themselves, surface unit/integration coverage, and deliver much quicker, actionable feedback.
AI-written summary · about
chapters (5)
- 0:00Start
- 0:10Being lazy- the perception
- 0:46Being lazy- my story
- 3:10Testing - Present state
- 5:14Testing - the lazy tester's way
