GlossaryQuality Gates

Quality Gates

Quality gates are automated checkpoints in a delivery pipeline that verify test results, code quality, and compliance before a change can merge or deploy.

Table of Contents

Table of Contents

How quality gates work

Quality gates act as gatekeepers in modern development. They evaluate whether a change meets defined standards before it moves forward.

  1. A change reaches a pipeline stage, such as a merge or deployment.
  2. The gate runs or collects required checks.
  3. Results are compared with thresholds.
  4. If every check passes, the change proceeds.
  5. If any check fails, the pipeline stops and developers get feedback.

Common quality gate criteria

  • Test results: all required suites pass
  • Coverage: minimum code or feature coverage met
  • Performance: latency and throughput within benchmarks
  • Security: no critical vulnerabilities, misconfigurations, or policy violations
  • Approvals: sign-off from specific reviewers or systems

Quality gates across pipeline stages

Layered gates catch different problems at the right time.

Stage Typical gate What it catches
Commit Unit tests and linting Logic and style errors
Pull request Integration tests and coverage Broken contracts and gaps
Pre-deploy Security scans and policy checks Vulnerabilities and misconfigurations
Post-deploy Smoke and performance tests Runtime and latency regressions

Why quality gates matter

Quality gates enforce consistency and reliability across development workflows. Automated enforcement cuts manual reviews and speeds delivery without lowering standards.

  • Consistency: every change meets the same bar
  • Speed: fewer manual reviews and faster approvals
  • Early feedback: problems fixed while they are cheap
  • Measurable quality: clear benchmarks to track over time

Real-world example

In a GitOps workflow, a merge request triggers automated tests through Testkube. A developer submits a change that adds a performance regression.

The performance gate fails, the merge is blocked, and the developer sees the results right away. The regression never reaches production.

Best practices

  • Business-critical metrics: gate on what matters to users, not just pass or fail counts
  • Realistic thresholds: start achievable and tighten as the codebase matures
  • Automated feedback: tell developers exactly why a gate failed
  • Multiple sources: combine test results, coverage, and security findings

Common pitfalls

  • Overly strict gates: block delivery and frustrate developers
  • Flaky tests: cause false failures and erode trust in gates
  • Poor observability: make gate failures hard to troubleshoot
  • No versioning: gate rules drift and are enforced unevenly

How quality gates relate to Testkube

Testkube integrates with CI/CD systems and GitOps pipelines to enforce gates with real test results from Kubernetes environments.

  • Automatic test runs: tests trigger before merges or deployments
  • Gate conditions: test outcomes decide whether a change proceeds
  • Many test types: functional, performance, and security tests in one gate
  • Clear results: logs and artifacts explain every failure

Frequently Asked Questions (FAQs)

Are quality gates only used in CI/CD?

Mostly, but GitOps workflows, release tools, and deployment platforms also use them.

What happens if a quality gate fails?

The pipeline stops, and the change cannot move forward until the issue is fixed.

How do quality gates differ from test suites?

A test suite runs tests. A quality gate decides whether results are good enough to proceed.

Can Testkube trigger or validate quality gates automatically?

Yes. Testkube runs tests before merges or deployments and its results act as gate conditions.

What metrics can be included in a quality gate?

Test pass rate, coverage, performance benchmarks, security findings, and required approvals.

How do flaky tests affect quality gates?

They cause false failures. Quarantine or fix flaky tests so gates stay trustworthy.

Related Terms and Concepts

Test Orchestration

Test orchestration coordinates when, where, and how automated tests run across tools, environments, and infrastructure so teams get reliable feedback without slowing delivery.
Read more

Continuous Quality Governance

Continuous quality governance is the ongoing, automated enforcement of testing standards, compliance policies, and quality controls across teams, clusters, and environments.
Read more

Continuous Testing

Continuous testing is the practice of running automated tests at every stage of the software delivery pipeline to give fast, ongoing feedback on quality.
Read more