liveBook · Manning

Quality gate

A quality gate is a checkpoint or criterion that determines whether work or an artifact meets specified requirements before proceeding to a later stage.

How 9 Manning books explain it

LLM Customization and Fine-Tuning

A check that determines whether generated or collected examples meet quality requirements before they are accepted into a dataset.

How it is used
Filters generated or collected candidates before dataset acceptance, including synthetic examples and mined production logs.
How deep it goes
Specifies a three-dimension scoring rubric, pass threshold, scoring function, and batch reporting procedure.
Examples
Scores financial sentiment sentences for label fidelity, realistic format, and plausible financial figures.
What you can do after
Operate a candidate gate using a scoring rubric and batch pass/fail reporting.

Read how LLM Customization and Fine-Tuning explains quality gate →

"Looks Good to Me"

A required validation or authorization that must be completed before a software change can advance in a delivery process.

How it is used
Protects code review by moving routine quality checks into merge-blocking validations.
How deep it goes
Defines PR gates, workflow placement, and machine-inspected criteria, but does not detail individual tool implementations.
Examples
Uses linting, formatting, sensitive-information checks, security checks, and GitHub’s prebuild merge check.
What you can do after
Apply it via pull-request checks and CI/CD gates to reserve human review for high-stakes issues.

Read how "Looks Good to Me" explains quality gate →

Automating API Delivery

A security quality gate is a pipeline control that permits progression only when security evaluation results satisfy a defined threshold.

How it is used
Applies automated controls before API proposals reach governance review or progress through deployment.
How deep it goes
Defines inputs, outputs, actors, triggers, risks, and controls, but leaves project-specific control selection open.
Examples
Uses BookInc's inconsistent BookStore API and a 42Crunch GitHub Actions security audit with a configurable passing score.
What you can do after
Operate/configure pipeline checks that block proposals failing defined API quality or security thresholds.

Read how Automating API Delivery explains quality gate →

Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform

How it is used
Coordinates infrastructure change reviews and delivery pipelines before production deployment.
How deep it goes
Defines review and test checkpoints, then explains staged delivery and batching risks without detailing gate implementation.
Examples
Uses change requests, peer review, testing environments, automated tests, and manual production approval as concrete gate artifacts.
What you can do after
Operate/configure delivery workflows that validate infrastructure changes before production release.

Read how Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform explains quality gate →

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.

How it is used
Uses deployment-pipeline conditions to prevent unready or badly timed changes from reaching production.
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 you can do after
Operate deployment pipelines with conditions that block production releases until readiness or timing requirements are met.

Read how Think Like a Software Engineering Manager explains quality gate →

Claude at Work

A quality gate is a predefined verification criterion that software must satisfy before progressing in a delivery process.

How it is used
Defines final checks for deciding whether software is ready to progress, such as before creating a pull request.
How deep it goes
Recommends selecting and running project-specific checks, but does not prescribe a universal gate or checklist.
Examples
Uses build, test, and run commands, Docker Compose healthchecks, and automated tests as verification examples.
What you can do after
Evaluate delivered work by running expected project checks and adding gates that meet your confidence needs.

Read how Claude at Work explains quality gate →

Shipping Go: Develop, deliver, discuss, design, and go again

A quality gate is a checkpoint that evaluates a product or work output before it proceeds to a subsequent production or delivery stage.

How it is used
Uses automated tests as an early pipeline checkpoint before building or shipping software.
How deep it goes
Explains the staged rationale and demonstrates test-before-build configuration, while deferring additional guards, builds, and deployments.
Examples
Uses a QA conversation, a cooking analogy, and a GitHub Actions workflow running Go tests before the build.
What you can do after
Operate/configure a CI pipeline that tests changes before allowing dependent build work to run.

Read how Shipping Go: Develop, deliver, discuss, design, and go again explains quality gate →

Build High Value Software Systems

A quality gate is a defined verification point that determines whether work satisfies specified quality conditions before proceeding.

How it is used
Uses a specification to define correctness and surface drift as work proceeds.
How deep it goes
Defines correctness and mismatch resolution, but does not specify automated enforcement.
Examples
Uses a CSV export specification covering user privacy, columns, encoding, and streaming.
What you can do after
Apply a specification to judge correctness and resolve implementation drift before it spreads.

Read how Build High Value Software Systems explains quality gate →

Vibe Engineering

A quality gate is a defined checkpoint that requires specified quality criteria to be satisfied before work can proceed.

How it is used
Uses defined checkpoints to control quality as agents and pipelines produce more of the Software Development Lifecycle.
How deep it goes
Explains the operational role of gates but stops short of specifying criteria, tests, or approval procedures.
Examples
Uses orchestrated agent fleets, sandboxing, rollback procedures, observability, and incident response as operational contexts.
What you can do after
Operate agent workflows by defining acceptance checkpoints and intervening when output drifts.

Read how Vibe Engineering explains quality gate →

Also covered in

What to know first

Related concepts

Questions about quality gate

What is quality gate?

A quality gate is a checkpoint or criterion that determines whether work or an artifact meets specified requirements before proceeding to a later stage.

Which Manning books explain quality gate?

LLM Customization and Fine-Tuning, "Looks Good to Me", Automating API Delivery, Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform, Think Like a Software Engineering Manager, Claude at Work, Shipping Go: Develop, deliver, discuss, design, and go again, Build High Value Software Systems and 1 more.

What should I know before learning quality gate?

Manning books that teach quality gate usually introduce deployment pipeline, software testing, experimentation and code coverage first.

What is quality gate part of?

Quality gate is part of pipeline. A pipeline is an ordered sequence of connected processing stages through which data or work flows, with each stage passing or transforming its output for subsequent stages.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.