liveBook · Manning

Smoke test

As explained in Effective Platform Engineering

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

A smoke test is a shallow operational check that confirms deployed services are broadly alive before deeper functional or integration testing. In a services pipeline, it checks container status while functional tests verify operating results. section 8.3.1

Control-plane deployment

After deploying kube-state-metrics, a shell test checks for a Running pod and a startup message. Separate checks query its metrics endpoint and inspect event-exporter output, moving beyond smoke coverage into functional verification.

How Effective Platform Engineering covers it

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 it assumes
Assumes familiarity with deployment pipelines, Kubernetes services, pods, and shell-based test assertions.
What you can do after
Diagnose deployment failures early by checking whether containers run and services report successful startup.
How it connects
Connects container status checks with functional tests, integration tests, Kubernetes deployments, and service logs.

Also explained in

Compare how 4 books explain smoke test →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Effective Platform Engineering. The section links point to the parts of the book it draws on.