What a good quality gate does
A quality gate is a decision point that uses automation signal to approve or block a release. A good gate catches real problems. A bad gate creates noise that engineers learn to ignore.
Essential gate checklist
- PR gate: Unit tests pass, linting clean, no critical security issues. Runs on every PR. Blocks merge on failure.
- Smoke gate: Critical user journey tests pass against the deployment. Runs after staging deploy. Blocks release on failure.
- Regression gate: Full regression suite passes with zero flaky failures. Runs before release decision. Advisory, not blocking (use flaky rate as the signal instead).
- Performance gate: Key response time and throughput metrics are within threshold. Runs on schedule. Alerts on regression.
Rules for gate design
- Every gate must have a clear owner who fixes it when it breaks.
- If a gate blocks a release with a false positive, fix the gate immediately — do not override it.
- Limit blocking gates to 2-3 per pipeline. More gates = less trust, not more quality.
What to do when a gate fails
Do not rerun. Investigate. If the failure is a real defect, fix it or make a deliberate risk decision. If it is a false alarm, fix the test and the gate. Rerunning trains the team to ignore the signal.