Why Everything Is SDET’ed and Spoiled
summary
The talk argues that test automation problems come from social and technical choices rather than tools alone, citing slow IE11 suites due to lack of parallelization, flaky UI tests from brittle locators, and costly rewrites/custom Selenium wrappers causing lock‑in. Concrete fixes include using Postman collections for fast feedback, JUnit with Gradle for unit and integration tests, adding a simple video recorder to capture failures, and agreeing with developers to ship static locators instead of brittle selectors.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 3:55Software testing problems
- 8:31Automation demand
- 16:36Myths about testers
- 25:10People and teams
- 36:33Career growth
- 44:40Testing tips
- 47:05Q&A
related talks
50mWhy Everything Is Spoiled
01h 48mNo Such Thing as Manual Testing and Other Confusions
46mFlaky, Fragile, and Forgotten: The Fall of a Test Automation Project
24mWHY ARE WE FAILING WITH TEST AUTOMATION?
51mRedefining test automation
37mSelenium In the Enterprise: What went right, what went wrong (so far)
01h 08mTest Automation Monsters
43mFrom Clickers to Coders: The SDET Evolution Story