Test to the standard and pass the quality gate
Learn how an AI-native org tests a change - the pyramid/trophy shape, the diff-coverage and mutation gates, flaky-test quarantine, the runnable harness, and the craftsmanship review bar - so you can test your own change and get it through the gate.
Units5
Duration25 min
Levelintermediate
By the end of this module, you'll be able to:
- Choose the right test shape and tier for a change, and apply the rule that overrides the ratios.
- Explain why coverage is a floor, why diff coverage is the blocking gate, and why mutation testing is the real adequacy gate for critical modules.
- Use the test harness - the runners, the inner and outer loop, and the gate-to-DoD map - to run the right tier and read the gate.
- Pass the code-craftsmanship review bar, favoring correctness by construction and never applying a principle dogmatically.
Prerequisites
- Basic familiarity with writing and running automated tests.
- Helpful, but not required: the "Apply the AGENTS floor" module.
Units
- 01Introduction4 min
- 02The testing standard7 min
- 03The test harness and the quality bar7 min
- 04Knowledge check4 min
- 05Summary3 min
Related
- Design and version an API Shape a clean, consistent API against a clear API design standard - resources, standard methods, typed errors, cursor pagination, idempotency - then version and deprecate it under a versioning policy so no consumer is ever broken without consent.
- Apply the naming standards Name a new identifier, file, repo, or branch the way an AI-native org does - keyword-first, no redundant prefix, cased by role - and tell a functional keyword apart from a product codename, so your first artifact passes the naming gate by default.
- Read the pipeline that ships your change Follow a change from a pull request through the canonical CI stage set to a gated production deploy - the ordered gates a pipeline runs, why CI is the real gate, and how the deployment model promotes one signed artifact dev to staging to prod.