Test classes and the release incidents each one catches

The playbook uses 12 test classes, from unit tests before merge to synthetic monitoring after deploy. Each incident page names one to three of them, labelled as cited in a public report or as by design analysis.

12 test classes

All test classes

ClassStageIncidentsCitedToolsProviders
Unit tests tests of one function or class in isolationpre-merge9194
Contract tests consumer and provider agree on request and response shape before deploypre-merge, pre-deploy9034
Integration tests real dependencies (database, queue, provider sandbox) exercised togetherpre-deploy214522
End-to-end tests user flows through the real UI against a deployed environmentpre-deploy, post-deploy1713251
Migration tests migrations run against a production-shaped copy with timing and rollback checkspre-deploy4381
Load and performance tests traffic replay or synthetic load with latency and resource budgetspre-deploy1431047
Security tests automated and manual checks for auth, authorisation, secrets and injectionpre-deploy311137
Configuration and environment tests checks that config, flags, secrets and endpoints resolve correctly per environmentpre-deploy, post-deploy24150
Compatibility tests the same flow across browsers, OS versions and device classespre-deploy202031
Canary and progressive delivery checks a small share of traffic runs the new version with automated metric comparisonpost-deploy26170
Synthetic monitoring scripted checks of critical flows against production on a schedulepost-deploy20260
Chaos and resilience tests injected failures (dependency down, latency, restart) to check degradation and recoverypre-deploy, post-deploy90112

Questions

What is test classes?

The site uses 12 test classes, each defined by what it catches and what it cannot catch.

Which incidents is test classes used for?

58 published incident types each list one to three test classes.