This standard ensures tests provide reliable, actionable confidence in code changes-so teams can move fast without sacrificing stability. Good tests catch issues early, reduce rework, and support safe, frequent releases.
Aligned to our "Engineering Excellence First" policy, this standard drives delivery confidence, improves quality, and reduces failure recovery time. Without it, teams ship with uncertainty, increasing the risk of regressions and user impact.
Clearly defined impacts of meeting this standard include improved delivery flow, reduced risk, higher system resilience, and better alignment to business needs. Over time, teams will see reduced rework, faster time to value, and stronger system integrity.
Level 1 – Initial: Testing is inconsistent or mostly manual.
Level 2 – Managed: Basic automated tests are in place but lack coverage and consistency.
Level 3 – Defined: Testing strategies (unit, integration, E2E) are consistently applied.
Level 4 – Quantitatively Managed: Test effectiveness and coverage are monitored and improved.
Level 5 – Optimising: Testing practices are adaptive, shift-left, and integrated into continuous delivery.