Quality Gate
A checkpoint in the development or deployment pipeline where predefined quality criteria must be met before the process can proceed to the next stage.
Quality gates enforce objective, automated standards at key transition points: before code is merged, before a build is promoted to staging, or before a release goes to production. They prevent known-deficient code from advancing. Typical criteria include minimum test coverage thresholds, zero critical or high-severity vulnerabilities, all smoke tests passing, and performance benchmarks met.
Tools like SonarQube, GitHub Actions, and GitLab CI can enforce quality gates automatically within CI/CD pipelines.
Why It Matters for QA Teams
Quality gates make quality enforcement automatic and consistent, removing the need for human gatekeepers to remember every check and preventing pressure to skip steps under deadline stress.
Example
A CI/CD pipeline has three quality gates: 1) Pre-merge: code coverage must not drop below 80%, no critical SonarQube issues. 2) Pre-staging: all integration tests pass, accessibility scan returns zero critical violations. 3) Pre-production: smoke tests pass on staging, load test confirms p95 response time under 500ms.