quality gate
A check, or set of checks, that a change must pass before it can move on, such as being merged or promoted to the next pipeline stage.
In more detail
A practical gate has layers: lint and type checks for fast feedback, tests for behaviour, and human review for judgement. A failing gate stops the change from going further, and canary releases can use an automated gate that compares health signals with a baseline. Useful gates protect a named risk, are reproducible from a clean checkout and raise few false alarms, so people trust them.
Example
Design system gates: token compilation, axe-core audits and visual regression comparisons on every pull request.Related terms
- continuous integration — Automatically building and testing every change as soon as it is pushed, so problems are caught early.
- axe-core — An open-source accessibility testing engine by Deque that checks rendered HTML against rules mapped to WCAG success criteria.
- visual regression testing — Testing that takes screenshots of components and compares them pixel by pixel with approved baseline images to catch unintended visual changes.
- pipeline — An automated sequence of steps, such as build, test, scan and publish, that runs on every change.
- canary release — Sending a small share of real traffic to a new version first, and increasing it only while its metrics stay healthy.
- linter — A tool that reads code or configuration without running it and flags likely mistakes and style problems.
- code review — A teammate reading a proposed change before it is merged, to understand it, catch mistakes and share knowledge.
- coverage gate — A rule that fails a build when code coverage falls below a set percentage.
Taught in
- A Testing Strategy In The Pipeline — Microsoft Azure DevOps Engineer Expert (AZ-400) Exam Prep
- Token Transformation: Style Dictionary & Multi-Platform Outputs — Design Systems & Component Engineering
- Automated Accessibility Testing: axe-core & Testing Library — Design Systems & Component Engineering
- Trunk-Based Development Versus Git Flow — DevOps & Site Reliability Engineering
- Continuous Integration — DevOps & Site Reliability Engineering
- Deployment Strategies: Canary Releases — DevOps & Site Reliability Engineering
- Coverage: Diagnostic, Not Target — Automated Testing, TDD & Quality Engineering
- Code Review As A Quality Gate — Automated Testing, TDD & Quality Engineering
- What To Automate Away — Automated Testing, TDD & Quality Engineering
References
- GitHub Docs: about protected branches
- Martin Fowler: DeploymentPipeline
- Martin Fowler: Continuous Integration
- Google engineering practices: the standard of code review