Predict Success in Production

The macro goal the eleven Test Desiderata properties serve: when the suite is green, shipping is safe; when it’s red, it isn’t. Bache’s Test Desiderata 2.0 names four macro desiderata: predict success in production, fast to get feedback, support ongoing code design change, low total cost of ownership. Beck’s Predictive property maps to the first. Singling that one out as the macro goal the other properties serve is this garden’s move, not Bache’s, and the field backs it as the load-bearing commitment: Fowler’s “when this suite goes green, we can release” is the same idea.

Inspiring confidence is this goal’s outcome, not a property: every proposed “inspiring” metric turns out to proxy something else: deployment frequency proxies speed and determinism, rollback rate proxies prediction. There is no Inspiring KPI; a team that wants confidence tunes the constituents.

The honest limit (Testing vs. Checking): automated checks predict only what was specified. An 80% mutation score can still ship the UX bug no test described. Green means “nothing we thought to check broke”; exploration covers the rest.

Measuring: change-failure rate (DORA elite: 0 to 15%), escaped defects per release, and mutation score on critical paths.

Sources

• Kent Beck, Test Desiderata: the Predictive property.
• Emily Bache, Test Desiderata 2.0: names it one of four macro desiderata and demotes Inspiring to an outcome. Singling it out as the macro goal is this garden’s move, not Bache’s.
• Martin Fowler, Software Testing Guide: “when this suite goes green, we can release.”