Angela Olszewska: Anti-tutorial: How to Terrify Your Team with Test Automation
summary
Shows concrete Python habits that break automation: toggling headless to headed so CI spawns visible browsers; running 1,000 one-minute tests sequentially versus 1,000 tests → 20 minutes with 50 threads to demonstrate parallel gains; deleting the README and dumping all files into one folder to make onboarding impossible; preferring long brittle XPath selectors over stable IDs and running a 1,000-run Selenium timing test that finds CSS vs XPath differences negligible; recommends headed only for debugging and tools like pytest, Selenium, SelectorsHub, BrowserStack.
AI-written summary · about
chapters (9)
- 0:00Welcome
- 1:28Switching to headed mode
- 5:24Sequential testing horror
- 12:13Unreadable test code
- 17:00Deleting README
- 21:25Chaotic folder structure
- 24:47Brittle selectors
- 30:01Anti-patterns summary
- 31:54Q&A
related talks
33mMore Than Automation: How Good Acceptance Test Can Make Your Team Happier
51mRedefining test automation
40mThe Test Automation Firehose
32mLiving on Crotches or UI Automation Antipatterns
54mTest Automation Transformation Avoiding the 7 Common Pitfalls
28mEgad! How Do We Start Writing Better Tests?
46mFlaky, Fragile, and Forgotten: The Fall of a Test Automation Project
24mA Comedy of Errors