Quality Gate
A checkpoint in a development or project process where predefined criteria must be met before proceeding to the next phase.
Also known as: Quality Checkpoint, Phase Gate, Stage Gate
Category: Software Development
Tags: quality, software-engineering, processes, automation, best-practices
Explanation
A Quality Gate is a formal checkpoint that enforces a set of conditions or criteria that must be satisfied before work can advance to the next stage. Originally from manufacturing and project management, the concept has been widely adopted in software development.
How Quality Gates work:
1. **Define criteria** - Establish measurable pass/fail conditions for each gate
2. **Automate checks** - Use tools to evaluate criteria automatically where possible
3. **Review results** - Assess whether all conditions are met
4. **Go/No-Go decision** - Either proceed, rework, or escalate
Common Quality Gates in software development:
- **Code commit gate** - Linting, formatting, and pre-commit hooks pass
- **Pull request gate** - Code review approved, tests pass, coverage thresholds met
- **Build gate** - Compilation succeeds, static analysis passes, no critical issues
- **Release gate** - Integration tests pass, performance benchmarks met, security scan clean
- **Deployment gate** - Staging environment verified, rollback plan in place
Benefits:
- Catches defects early before they propagate downstream
- Enforces consistent quality standards across teams
- Provides clear, objective pass/fail criteria
- Creates accountability and visibility into quality metrics
- Reduces cost of fixing issues found late in the process
Tools like SonarQube, Jenkins, GitHub Actions, and GitLab CI/CD can enforce Quality Gates automatically in CI/CD pipelines. The key is finding the right balance: too few gates let defects through, while too many gates slow delivery and frustrate teams.
Anti-patterns:
- Gates so strict that teams game the metrics rather than improve quality
- Manual-only gates that become bottlenecks
- Gates without clear ownership or escalation paths
- Ignoring gate failures under deadline pressure
Related Concepts
← Back to all concepts