No Such Thing as Manual Testing and Other Confusions
summary
Argues that testing quality depends on concrete engineering choices, not slogans, and identifies anti-patterns like huge undocumented automated UI test suites (300–500 checks), fragile Selenium end-to-end tests, brittle assertions that lack diagnosable messages or proper matchers, hardcoded credentials and embedded configs, and overengineered wrapper layers. Recommends favoring a majority of unit tests, mapping manual cases clearly to automation, using command-line configuration, and keeping tests independent and small to reduce maintenance debt.
AI-written summary · about
chapters (5)
- 0:00Introduction
- 52:26Testing anti-patterns
- 1:03:52Automation anti-patterns
- 1:17:14Code anti-patterns
- 1:36:36Q&A
related talks
41mNo Such Thing as Manual Testing and Other Confusions
51mRedefining test automation
39mTen things you heard about testing that might be wrong
42mOpening Keynote: Blunders in Test Automation
57mAdvanced Testing Techniques: Tips from the trenches
47mIs Survival of the Fittest Only for the Fastest?
40mThe Test Automation Firehose
13mBeyond the hype: What test automation really costs