liveBook · Manning

Smoke test

Also called smoke testing

A smoke test is a brief, shallow test of essential system functions to determine whether a build or deployment is sufficiently operational for further testing or use.

How 5 Manning books explain it

Effective Platform Engineering

A smoke test is a shallow test that checks whether a system or service is broadly operational before deeper testing.

How it is used
Uses shallow pipeline checks to establish that deployed services are operational before deeper verification.
How deep it goes
Checks container status and startup evidence, then stops short of verifying operating results covered by functional tests.
Examples
Demonstrates Running pods, successful startup logs, metrics endpoints, and event-exporter output from Kubernetes services.
What you can do after
Diagnose deployment failures early by checking whether containers run and services report successful startup.

Read how Effective Platform Engineering explains smoke test →

Machine Learning System Design

A preliminary test that checks whether a system or component operates sufficiently to warrant further testing.

How it is used
Checks ML training pipelines after changes before engineers spend time on deeper testing or experimentation.
How deep it goes
Defines a fast, reduced-scale pipeline check and its maintenance tradeoff, while deferring detailed component coverage to unit tests.
Examples
Uses a fixture dataset, one epoch, a dummy ResNet, mocked construction, and training and validation loss assertions.
What you can do after
Diagnose/debug pipeline regressions quickly and decide whether deeper testing or experimentation is worthwhile.

Read how Machine Learning System Design explains smoke test →

Learn Docker in a Month of Lunches, Second Edition

A smoke test is a short, focused test that checks whether a software build or deployment performs its essential functions.

How it is used
Uses minimal end-to-end checks to verify application builds within a CI/CD pipeline.
How deep it goes
Explains the Docker Compose workflow and image choices, but stops short of detailed test design or browser automation.
Examples
Demonstrates a PowerShell script, local-image execution, staging-image execution, web requests, and container shutdown.
What you can do after
Apply it via Docker Compose and PowerShell to check whether an application starts and responds during a build.

Read how Learn Docker in a Month of Lunches, Second Edition explains smoke test →

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

A small, rapid set of tests that checks whether critical functionality remains operational after a change.

How it is used
Provides rapid feedback after changes before teams invest time in the full end-to-end test suite.
How deep it goes
Defines the test and gives infrastructure scenarios, but stops short of detailing a complete smoke-test suite.
Examples
Uses Cloud Run URL checks, network connectivity, workload completion, and HTTP requests with varying payloads.
What you can do after
Apply it via pytest and infrastructure workflows to detect catastrophic change failures before further testing.

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

LLM Customization and Fine-Tuning

A smoke test is a basic test that checks whether essential parts of a software system run successfully.

How it is used
Catches broken prompts, training setup errors, or code failures before evaluation or costly GPU runs.
How deep it goes
Checks execution and obvious failures, but does not rank close prompt variants or replace larger release evaluations.
Examples
Uses 20 production-log inputs for prompts, short training runs for SFT, and CPU execution on a laptop.
What you can do after
Apply it with a small held-out prompt set or --max_steps 2–5 to catch failures before full evaluation or training.

Read how LLM Customization and Fine-Tuning explains smoke test →

Also covered in

What to know first

Related concepts

Questions about smoke test

What is smoke test?

A smoke test is a brief, shallow test of essential system functions to determine whether a build or deployment is sufficiently operational for further testing or use.

Which Manning books explain smoke test?

Effective Platform Engineering, Machine Learning System Design, Learn Docker in a Month of Lunches, Second Edition, Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform and LLM Customization and Fine-Tuning.

What should I know before learning smoke test?

Manning books that teach smoke test usually introduce accuracy, deployment pipeline, epoch and integration test first.

What is smoke test a kind of?

Smoke test is a kind of end-to-end testing. End-to-end testing evaluates a complete system workflow across integrated components, from an external entry point to its observable outcome.

What is smoke test also called?

Smoke test is also called smoke testing.

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.