Self-Healing or Self-Killing?
summary
Eighteen months of running >1,000 nightly e‑commerce tests with AppliTools, WombTest and open source Helenium shows concrete outcomes: Helenium is integrated by overriding findElement, extended to record URL and market and to skip self‑healing for invisibility conditions, but only 5% successful automatic repairs and 90% negative impact where wrong elements are clicked. Teams spend more time triaging healed passes, PayPal sandboxes and selector scoring breakings occur, so the decision is to stop using self‑healing for now.
AI-written summary · about
chapters (17)
- 0:00Introduction and speaker intro
- 1:34What is self-healing automation
- 2:38History and myths of self-healing
- 4:44Why we tried self-healing
- 5:49Context of our e-commerce tests
- 7:37Self-healing expectations and use cases
- 9:03Evaluating self-healing tools
- 11:13Helenium setup and first results
- 14:20First challenge with Helenium
- 16:25PayPal integration issues
- 18:10Invisibility and expected conditions
- 19:14Wrong element selection by Helenium
- 21:04Final Helenium results and analysis
- 22:32Lessons learned from self-healing
- 24:22Decision to stop using self-healing
- 25:24Future hope with data-auto-id attributes
- 27:12Q&A session
related talks
25mSelf-Healing in Test Automation
30m'Self-Healing Tests' - The holy grail of test automation?
44mSelf-healing Test Automation 2.0: The Future
55mStability in Unstability: Self‑Healing Test Automation
54mStability in Unstability: Self-Healing Test Automation
32mSelf-healing system for UI tests using ML
54mSelf-Healing Automation with Healenium and Regression Minimization with Drill4J
42mEnhancing Appium Tests' Stability with the Power of Healenium