TestingBudget

Run

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.

Also called: defect confirmation · bug verification · failure triage · defect review

Unit
minutes per failure and per defect
Where you enter it
Run tab, per vendor: "Triage one failure" and "Write up one defect". The defect count is the application's "Defects found per run".

What it means

After a run, an automation tool has produced failures, not defects. Defect validation is the work of turning one into the other: reproduce the failure, rule out the false positives — a broken test, an environment problem, a flake — and, for the ones that survive, document the bug well enough that a developer can act on it. It is the largest recurring human cost of running an automated suite, and the one an execution-speed comparison never shows.

The model prices it as two activities rather than one number, because they scale with different things. Triage is paid once per failure, real or not, so it multiplies with the tool's false-positive rate. Write-up is paid once per confirmed defect, so it multiplies with how many bugs the product actually has and is the same for every tool. Splitting them is what lets the model show that a tool with better diagnostics saves triage time without pretending it finds fewer bugs.

It is not the same as validating a built case, which happens once in the Build phase and checks that a new test asserts the right thing.

Why it matters to the cost

On the default suite a tool sees about sixteen failures a run; at twenty minutes of triage each and twenty more to write up each of the five real defects, defect validation is roughly seven hours per run — eighty-plus hours a year at twelve runs, before a single test is repaired. It is where a tool's failure diagnostics (screenshots, traces, root-cause hints) earn their licence, and it is the number to measure in a proof of concept: run the suite against a known-bad build and time the validation.

Typical values

Thirty minutes of triage per failure with basic reporting, ten to fifteen with good diagnostics; fifteen to thirty minutes to write up a confirmed defect. For manual testing only the write-up applies: the tester validates as they execute.

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.

The formulas it lives in

Run — every release

tests broken per run
Total test cases × Test breakage rate ÷ Runs per year — found here, repaired under Maintain
Failures per run
Defects found per run + tests broken per run + flaky per run — derived, never asked
Machine time per run
Total test cases × Execution time per case — automation only; duration, not labour

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

Try it with your numbers

The calculator works defect validation out from the rows it is built on. Change those and every total on the page moves with them — free, in your browser, nothing to install.

See how defect validation impacts the calculation of test automation costs

Last reviewed 2026-09-15. All terms.