TestingBudget

Run

Triage one failure

The time to look at one failing test and decide what it is: a real defect, a broken test, an environment problem, or a flake.

Also called: failure analysis · root-cause analysis · defect validation (the deciding step)

Unit
minutes per failure
Where you enter it
Run tab, per vendor.

What it means

After an automated run, every failure needs a person to classify it. The standard method is to re-run on the same commit: a pass on retry is a flake, a repeated failure is real — and then to decide whether "real" means the product or the test. The time this takes depends heavily on the tool's diagnostics: screenshots, logs, step-level traces and root-cause hints shorten it.

It applies only to automation vendors. A manual tester decides what a failure means as they execute it, so there is no separate triage step.

Why it matters to the cost

Multiplied by failures per run and runs per year, triage is usually the largest human cost of running an automated suite. Microsoft's figure of about thirty minutes per investigation, on sixteen failures a run, is eight hours a run; a tool whose diagnostics halve that saves four hours every cycle. It is one of the two per-tool numbers an evaluator can genuinely measure in a proof of concept.

Typical values

Around thirty minutes with basic reporting; ten to fifteen minutes with good diagnostics. Not applicable to manual testing.

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

Run — every release

tests broken per run
Total test cases × Test breakage rate ÷ Runs per year — found here, repaired under Maintain
flaky per run
Total test cases × Flaky failures per run
Failures per run
Defects found per run + tests broken per run + flaky per run — derived, never asked
Run effort
Prepare and start a run + Failures per run × Triage one failure + Defects found per run × Write up one defect + Report and sign off — an automation tool
Run effort
Prepare and start a run + Total test cases × Execution time per case + Defects found per run × Write up one defect + Report and sign off — a manual approach — the tester is the run
Machine time per run
Total test cases × Execution time per case — automation only; duration, not labour
Run cost per year
Run effort per run × Runs per year × Effective hourly rate + Token cost

Every name is a link to its definition. See the whole model.

Try it with your numbers

Triage one failure 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 triage one failure impacts the calculation of test automation costs

Related terms

  • Defect validation The human work of proving that a failed test is a real product defect and getting it in front of a developer — priced as triage per failure plus write-up per defect.
  • False positives per run Test failures that are not product defects — tests the product broke plus flaky failures. The model counts both, on separate rows, because they have different owners.
  • Failures per run Everything a person has to look at after a run: defects found plus tests the product broke plus flaky failures — derived, never typed.
  • Flaky failures per run The share of cases that fail for no product reason — timing, environment, brittle selectors — and still have to be investigated.
  • Write up one defect The time to reproduce a confirmed defect, log it with steps and evidence, and hand it to development.
  • Run effort The person-hours a run costs — preparation, triage, defect write-up and sign-off for a tool; execution itself for manual testing — and the same figure over a year.

Last reviewed 2026-09-15. All terms.