Panel Discussion: Future of Test Automation
summary
Claims that tool dependency grows are backed by examples: a client runs 2 million executions a quarter and needs governance, a Chrome auto-update Chrome update broke thousands of UI tests that stalled CI, and vendors push AI features like an automation fabric centralizing test data and up9.com auto-generates API tests from specs. Promises include an "echo database" that learns app behavior over time and a test browser prototype that auto-generates scripts; success depends on monitoring, mitigation plans, and whether those artifacts actually scale.
AI-written summary · about
chapters (8)
- 0:00Panel introduction
- 3:03Future of test automation
- 11:29Tool dependency vs DIY
- 16:06Selecting tools by goals
- 25:08Team organization for automation
- 34:40Addressing audience questions on automation
- 44:39Common automation mistakes
- 46:24Closing remarks
related talks
44mThe future of test automation
39mPanel Discussion: Future of Testing: Will Test Automation Put Manual Testing into the Shade?
01h 08mTest Automation Monsters
44mThe Future of Test Automation
39mPanel Discussion | Mastering Test Automation: Strategies and Innovations
59mThe Future of automated testing
01h 04mImpact of AI on #SoftwareTesting: Are Testers Ready? 🔮
45mPanel Discussion | Test Automation Trends
