Is Survival of the Fittest Only for the Fastest?
summary
Argues that manual testing survives because automation often fails in practice: unattended CI/CD batches stop for server updates or screensavers, large automated suites slow pipelines, and combinatorial scripts waste runs. Cites real tools and patterns (page‑object models, CI pipelines, Excel data matrices) and concrete fixes: smoke/sanity checks, log inspection, selective combination reduction. Recommends shifting toward design/analysis work, using automation paradox and automation blindness as diagnostics and running regular lean coffee sessions.
AI-written summary · about
chapters (14)
- 0:00Manual testing introduction
- 1:09Evolution of manual testing
- 2:33DevOps and automation impact
- 4:45Why manual testing matters
- 6:51Automation fake news pitfalls
- 11:08Automation paradox in agile
- 13:59Automation blindness effects
- 17:32Future of manual testers
- 18:13From sheep to no-sheep tester
- 21:51Focus on critical testing
- 27:09Informal communication and fika
- 33:51Global and local testing
- 41:05Summary and future skills
- 42:11Q&A on automation and salaries
related talks
16mIsn’t Test Automation a Silver Bullet?
21mThe Essential Pillars of Automation Testing for Success
01h 48mNo Such Thing as Manual Testing and Other Confusions
50mWhy Everything Is Spoiled
40mThe Test Automation Firehose
01h 08mTest Automation != Less Testers || Faster Testing || More Time For ET
24mWHY ARE WE FAILING WITH TEST AUTOMATION?
47mWhat Successful Test Automation is... and Why it's NOT Testing!