Auto Heal · Self-healing locators
When selectors drift, your tests don't break.Auto Heal repairs broken Selenium locators at runtime. Deterministic DOM rules first. AI-browser second, only when deterministic confidence is low. Your test code stays the way you wrote it. The session goes green.
|
Heal mode
No code change
Common case
Sub-100ms
Activation
1 flag
Selenium Box · Self-Healing Locator
Healing locators · live
Attempts 3
Success 3
Failed 0
Deterministic · DOM scan + role/name rules. Fast. No model.
AI-browser · Used only when deterministic confidence is low.
|
Auto Heal absorbs locator churn from frontend deploys. Release-day regression doesn't go red over selector hygiene.
Compliance-firstEvery heal logs a plain-English rationale. Defensible to QA leadership and compliance reviewers.
Audit trailDeterministic mode handles the majority of heals with DOM rules. AI engages only when needed. Less budget, less attack surface.
Air-gap readyAdd e34:autoHeal: true to your capabilities. Existing specs stay untouched. Maintenance hours drop immediately.
Zero-touch enablementEvery long-lived Selenium suite carries the same maintenance cost. A frontend rename. An A/B test. A library upgrade. One selector goes stale and the next run is red. Auto Heal repairs the drift at runtime. Your test code stays the way you wrote it.
Symptom. #usernames becomes #username, #Pass becomes #password, #$ubmit becomes button[type='submit']. Same intent, new attribute. Test fails with NoSuchElementException.
Symptom. Design system swaps a div button for a real button element. CSS selectors lose. The change was intentional and correct.
Symptom. Copy changes per locale or experiment cohort. Text-based selectors fail in DE-AT but pass in EN-US. Suite goes flaky.
Auto Heal never reaches for the model when DOM rules can do the job. That keeps healing fast, cheap, and explainable. The AI-browser tier only engages when deterministic confidence is below threshold. Both modes log their reasoning to the session record.
DOM scan plus role and name rules. Sub-100ms decision, no model invocation. Most heals resolve here, especially typos, casing changes, and ID renames.
LLM-based reasoning over the DOM. Engages only when deterministic confidence is low. Returns a ranked candidate list with confidence scores and a plain-English rationale.
The same login spec runs against the same DOM. The only difference is one capability in the WDIO config: e34:autoHeal. Without it, three broken selectors red the suite. With it, three heals happen at runtime and the suite stays green.
Test code is identical in both runs. Only the e34:autoHeal capability changed.
Add a single capability to your WDIO config. Auto Heal applies to every test in the session. Your existing Selenium specs do not change.
Auto Heal is not a silent magic layer. Every healing decision writes to the session record with three artifacts: the requested selector, the used selector, and a plain-English rationale. QA leadership and compliance reviewers see what changed and why.
e34:autoHeal.
Every heal records the exact selector your test asked for and the selector Auto Heal substituted. No silent rewrites.
AI-browser heals include a plain-English explanation. Auditors and engineering reviewers see why a selector was changed.
Every heal is ranked. Candidates listed with confidence bars. Reviewers can accept or reject suggestions before they ship to nightly runs.
Point Auto Heal at the LLM you already trust. Heal prompts run between SBOX and your AI provider only. Element34 never sees the DOM or the prompt.
Deterministic mode handles the common heals without an LLM call. You spend tokens only on the hard cases. Configure in your SBOX config to point at the model of your choice.
Use your OpenAI, Anthropic, or Azure OpenAI subscription. Or a self-hosted model running inside your environment.
Deterministic resolves most heals with zero model calls. AI-browser engages only when deterministic confidence is low. Token monitoring per project lands in SBOX 5.2.4.
Heal logs stay inside the customer environment. Element34 has no visibility into your DOM, your selectors, or your AI prompts.
Auto Heal keeps long-lived suites green. Studio authors the tests. Automated RCA diagnoses the failures. Pulse Report scores the release. Real Device Cloud runs on iOS and Android. All five run on your private SBOX grid.
Plain-English to production-grade Selenium. Studio writes the test, Auto Heal keeps it alive.
Explore Studio →Cluster failures, summarize root cause, propose fixes. Where Auto Heal handles drift, RCA handles failure.
Explore Automated RCA →Site health with prioritized opportunities. Pulse reads the session record Auto Heal writes to.
Explore Pulse Report →Real iOS and Android devices. Auto Heal applies to real-device sessions the same way it applies to desktop.
Explore Real Device Cloud →Send the spec. We add e34:autoHeal: true on your private grid and run it. You see every healed locator, every confidence score, and every AI rationale before any code review. Annual licensing, predictable across the contract term. Talk to sales for a scoped quote.