A Comedy of Errors
summary
Claims that after trying Java then Python for years the automated suites are brittle tests that need fiddling every run, concedes five years of struggle before stopping hands‑on automation, and reports exploratory testing consistently finds the best bugs. Notes concrete tooling: Git via terminal, reading repos and commit messages, installing a password manager for nontechnical users. Positions as an automation advocate who delegates coding to engineers, pushes for addressing technical debt, and measures success by reduced toil not feature count.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:11Automation to advocacy struggles
- 2:34Coding frustration signs
- 4:23Coding vs exploratory testing
- 6:40Tool installation woes
- 8:50Bad managers impact
- 10:17Critiquing automation models
- 12:44Cultural differences in tech
- 15:35Tech mishaps stories
- 17:25Becoming automation advocate
- 19:38Summary
- 21:01Q&A
related talks
42mOpening Keynote: Blunders in Test Automation
23mIntersection of Automation and Exploratory Testing
50mAsaf Shochet Avida, Eitan Noy: Why My Amazing Test Automation Project Crumbled
21mThe Essential Pillars of Automation Testing for Success
50mWhy Everything Is Spoiled
51mRedefining test automation
40mThe Test Automation Firehose
01h 48mNo Such Thing as Manual Testing and Other Confusions