What a quality gate does
A quality gate is a decision point that uses defined evidence to determine whether a change may progress to the next delivery stage.
A gate should protect meaningful risk—not create ceremony.
Examples of automated gates
- Build succeeds
- Unit tests pass
- Critical API tests pass
- Security scan threshold met
- Code-quality threshold met
- No schema-breaking change
- Smoke suite passes
- Deployment health passes
Examples of manual or governed gates
- High-risk architecture approval
- Security exception
- QA release recommendation
- Business acceptance
- CAB / change approval
- Operational readiness
Design gates around severity
| Condition | Possible gate response |
|---|---|
| Critical test fails | Block automatically |
| Low-risk test fails | Continue with warning / review |
| Known environment issue | Pause or invoke controlled exception |
| Security critical finding | Block pending resolution/exception |
Avoid brittle gates
If unreliable tests block delivery frequently, teams will pressure the organization to bypass the gate. Gate reliability therefore depends on stable tests, environments, data, and ownership.
Make exceptions visible
Exceptions should be explicit, time-bound, owned, and auditable. Silent bypasses destroy the credibility of quality gates.