Maintain
Review one heal
The time to confirm an automatic repair did the right thing before trusting the test again.
- Unit
- minutes per heal
- Where you enter it
- Maintain tab, Detailed mode, per vendor.
What it means
When a tool heals a case on its own, someone checks that the new locator or step still tests what the case was meant to test. The task is approving rather than fixing, so it is short — but a suite where heals go unreviewed will drift toward passing for the wrong reasons.
Multiplied by the cases healed, it is the price of self-healing in the maintenance line.
Why it matters to the cost
Five minutes a heal on 30 heals a year is under three hours — the whole point of self-healing, made visible. Leaving the line out would let a vendor's claim look like free maintenance; including it keeps the comparison defensible.
Typical values
Around five minutes per heal.
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
Review one heal 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 review one heal impacts the calculation of test automation costsLast reviewed 2026-09-15. All terms.