Smoke Test

A smoke test is a small, focused test case that checks one critical function or flow in a build, serving as the individual unit within a broader smoke testing suite used to verify basic application stability.

A smoke test, as an artifact, is a single test case scoped to one essential capability — for example, verifying that the login endpoint returns a valid session token, or that the checkout page loads without a server error. Each such test case is deliberately narrow and fast-executing, targeting a specific critical path rather than edge cases or detailed validation.

Smoke tests are authored to be independent and self-contained so they can be assembled into a suite and executed in any order. Their pass/fail result is binary and unambiguous: either the targeted function responds as expected or the build is considered unstable. This binary clarity is what makes each individual smoke test useful as a build acceptance criterion.

In practice, a smoke test case is distinguished from a full functional test case by its scope constraints: it asserts only that a feature is reachable and returns a recognizable response, not that every business rule within that feature is correct. This deliberately limited scope is what allows a collection of smoke tests to complete within minutes rather than hours, making them viable as an entry-criteria gate before deeper test phases begin.