Self-Healing in Test Automation
summary
Claims that AI-driven self-healing cuts UI test maintenance and flakiness while reducing the ~30% maintenance budget hit come with specifics: Selenium UI use resurfaces, JavaScript test tooling fragments, and solutions range from heuristics toward neural networks for prediction. A working approach detects changes, diagnoses failures against a golden baseline, and attempts adaptation, but adaptation is the hardest part, always-passing tests and vendor snake oil are real risks, and recommended practice is start small fail fast and measure what actually heals.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 0:47Mindset shift
- 2:12Unrealistic expectations
- 4:03Untestable code
- 6:05Maintenance
- 7:45AI
- 8:51Unlimited Money
- 10:51Chatbots
- 11:17AI Solutions
- 13:56Why do we need selfhealing
- 14:14Why do we want selfhealing
- 14:46What is selfhealing
- 15:51Level of selfhealing
- 16:53Confidential bluffing
- 17:22Oracle Question
- 18:00Prediction Question
- 18:38Challenges
- 18:55Vision
- 19:17Future
- 19:50Questions Answers
related talks
44mSelf-healing Test Automation 2.0: The Future
30m'Self-Healing Tests' - The holy grail of test automation?
41mHow AI is transforming software testing
31mSelf-Healing or Self-Killing?
16mTransforming Test Automation with AI and Machine Learning
51mRedefining test automation
43mSmart and Stable Automated Testing Using AI Based Dynamic Locators
18mSay Goodbye to Test Automation Flakiness Using Next-Gen AI Tools