liveBook · Manning

Quality gate

As explained in Think Like a Software Engineering Manager

A quality gate is a release-control condition that must be satisfied before software can proceed to a later delivery stage.

A quality gate is a release-control condition that software must satisfy before deployment can continue. It acts as a guardrail, stopping changes that are not ready or whose timing is inappropriate. section 12.2.4

Common deployment gates include:

  • Test coverage rules that block changes when required coverage is not met. section 12.2.4
  • Date and time restrictions that prevent deployment during unsuitable windows. section 12.2.4
  • Product launch-date constraints that coordinate deployment with planned releases. section 12.2.4

A deployment pipeline blocker

A pipeline can stop a production deployment when its test-coverage rule is unmet, preventing incomplete changes from progressing until the condition is satisfied. section 12.2.4

How Think Like a Software Engineering Manager covers it

How deep it goes
Defines gates and gives representative conditions, but does not detail their implementation or configuration.
Examples
Uses test coverage rules, date and time restrictions, and product launch-date constraints as deployment blockers.
What it assumes
Assumes familiarity with software deployment and production releases, while explaining the gate role in plain operational terms.
What you can do after
Operate deployment pipelines with conditions that block production releases until readiness or timing requirements are met.
How it connects
Connects quality gates with deployment checklists, dashboards, alerts, and rollback procedures.

Also explained in

Compare how 5 books explain quality gate →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Think Like a Software Engineering Manager. The section links point to the parts of the book it draws on.