Maintain
Self-healed cases per year
The share of broken cases an AI tool repairs on its own — which then need a person to confirm the repair was right.
- Unit
- % of cases per year
- Where you enter it
- Maintain tab, Detailed mode, per vendor.
What it means
Self-healing tools detect a broken locator or step and propose or apply a fix automatically. This rate is the share of the suite healed that way in a year. It does not remove the human: current practice is that every heal is reviewed before it is trusted — some tools surface heals in an approval queue, others open a change request per healed case.
It is separate from the breakage rate. A tool with self-healing typically has a low breakage rate (heals are not counted as breakages) and a heal-review cost instead.
Why it matters to the cost
Vendors present self-healing as removing maintenance. Costed honestly it converts it: a repair that took forty-five minutes becomes a five-minute review. That is a real and large saving, but it is not zero, and pricing it as zero is how an evaluation gets challenged later.
Typical values
AI-native tools around 10% of cases a year; other categories none.
Typical values describe a category of tool — AI-native, codeless, script-based, homegrown, manual — never a named product. Why we do not price named products.
Where it appears in the model
Maintain — continuously
- cases to repair
- Total test cases × Test breakage rate
- cases healed
- Total test cases × Self-healed cases per year
- Maintenance effort per year
- cases to repair × Repair time per case + cases healed × Review one heal + Platform upkeep per year + New cases added per year × Build a new case
Every name is a link to its definition. See the whole model.
Try it with your numbers
Self-healed cases per year is a row in the calculator. Change it and every total on the page moves with it — free, in your browser, nothing to install.
See how self-healed cases per year impacts the calculation of test automation costsLast reviewed 2026-09-15. All terms.