Skip to main content
Strategy & Process

What Is Quality Gates?

Quality gates are checkpoints in the software delivery process where predefined quality criteria must be met before work can proceed to the next stage, enforcing minimum standards at each phase.

Start a Free Mock Interview

Free to start · 7-day trial on paid plans

In Depth

Quality gates act as automated or manual tollbooths in your delivery pipeline. Each gate has specific pass/fail criteria. A commit-level gate might require passing linting and unit tests. A PR gate might require code review approval, minimum test coverage, and no new security vulnerabilities. A pre-production gate might require passing integration tests, performance benchmarks, and accessibility scans. A release gate might require stakeholder sign-off and successful smoke tests in staging.

The most effective quality gates are automated and integrated directly into CI/CD pipelines. When a developer pushes code, the pipeline runs each gate sequentially and blocks progression if any gate fails. This removes human bias and ensures consistency. Tools like SonarQube, GitHub Actions branch protection rules, and Argo CD sync policies enable automated gating.

The risk of quality gates is over-gating: too many gates or overly strict criteria slow delivery to a crawl. The solution is to calibrate gates to the risk level of each stage. Early gates should be fast and lenient (linting, unit tests). Later gates can be thorough and strict (full regression, performance benchmarks).

Why Interviewers Ask About This

Interviewers ask about quality gates to see whether you can design and enforce systematic quality controls. This is a key skill for QA leads and SDETs who shape delivery processes.

Example Scenario

A team implements three quality gates: PR gate (unit tests, lint, coverage >= 80%), staging gate (integration tests, zero critical bugs), and release gate (smoke tests pass in production-like environment, load test meets SLA). A developer's PR is blocked because coverage dropped to 76%. They add two unit tests and the gate passes on the next push.

Interview Tip

Describe quality gates you have implemented or improved. Be specific about the criteria at each gate and how you balanced thoroughness with delivery speed.

Related Terms

Explore related glossary terms to deepen your understanding.

Continuous TestingContinuous testing is the practice of executing automated tests at every stage of the CI/CD pipeline, providing immediate feedback on the risk level of each code change as it moves toward production.
Definition of DoneThe Definition of Done (DoD) is a shared checklist of quality conditions that every user story, feature, or increment must meet before it can be considered complete, covering aspects like testing, documentation, code review, and deployment readiness.
Shift-Left TestingShift-left testing is the practice of moving testing activities earlier in the software development lifecycle, catching defects during requirements, design, and development rather than after deployment.
Test StrategyA test strategy is a high-level document that defines the testing approach, objectives, scope, types of testing, environments, tools, and risk mitigation for a project or organization.
Smoke TestingSmoke testing is a shallow, broad test run that verifies that the most critical features of an application are working after a new build or deployment, acting as a quick go/no-go decision.

Related Resources

Dive deeper with these related interview prep pages.

Jenkins Interview QuestionsGitHub Actions Interview QuestionsSDET Interview PrepQA Methodology Questions

Ready to Ace Your QA Interview?

Practice explaining quality gates and other key concepts with our AI interviewer.

Join 1,200+ QA engineers already practicing with AssertHired.

Start Your Free QA Interview

Free to start · 7-day trial on paid plans

Written by Aston Cook, Senior QA EngineerLast updated: March 2026