Test Automation Monsters
summary
Conference claim: digitalization and DevOps force “automate everything” but reality is tool churn and fragility. Organizers name Selenium, Cypress, Playwright as swapping-era examples; teams hit flaky results and maintenance so often that manual retest runs faster. Surprising timelines show Google saying “testing is dead” ~10 years ago and agile shifts 15–20 years ago. AI/ML gets hyped but underdelivers; proposals like self‑healing tests and autonomous assistants exist but rarely work reliably yet, and people leave once upskilled.
AI-written summary · about
chapters (21)
- 0:00Intro
- 2:30Welcome to the Screen Factory
- 7:17Tools
- 9:51Stability Reliability
- 13:04Testing is dead
- 16:08Testing is technical work
- 20:36The biggest monster
- 22:01Scaries and scares
- 25:41AI and machine learning
- 26:51The future of testing
- 29:14What is testing
- 33:31The biggest test automation monster
- 35:46Digital vs physical businesses
- 38:31SDQB
- 42:31Manual vs Automation
- 44:16Automation vs Manual
- 45:46Communication
- 51:01New approach
- 53:01Hiring people
- 55:31Leaving testing
- 57:44API vs UI
related talks
47mPanel Discussion: Future of Test Automation
46mEvolution & Future of Software Testing
51mRedefining test automation
21mThe Essential Pillars of Automation Testing for Success
16mIsn’t Test Automation a Silver Bullet?
32mWhy testing is a developer's problem
38mNext Generation Testing in the Age of Machines
44mWe’ve Got DevOps — Let’s Fire All Testers