#9DELIVERYBUILD
Quality Gates
Tests, linting, type checking, coverage
Easy
Overview
Automated quality checks that must pass before code can proceed. Includes unit tests, linting, type checking, and coverage thresholds.
Why It Matters
Pipeline fails if code is broken. No manual 'did you run tests?' conversations.
The Risk
Without enforcement, quality degrades gradually. Tests get skipped when deadlines loom. Technical debt accumulates. Bugs that tests would catch reach production.
Implementation Components
A complete implementation of this capability includes:
- Automated test suite (unit, integration)
- Code linting and formatting checks
- Type checking (TypeScript, mypy, etc.)
- Coverage thresholds that block merge
- CI pipeline that fails on any gate failure
- Fast feedback - gates should run in minutes
Implementation Pattern
- 1Define required checks
- 2Set coverage thresholds
- 3Configure CI to block on failures
- 4Track quality metrics over time
Tool Examples
These are examples, not endorsements. Choose what fits your context.
Dependencies
Requires (must have first)
Enhanced by (more effective with)
Enables (unlocks)
Same Phase
Other capabilities in this pipeline phase