Smoke Test

A smoke test is a shallow, broad check that confirms an application's core functionality is intact. The term originates from hardware engineering, where powering on a new circuit board and checking that nothing literally smokes is the first validation step. In software, smoke tests serve the same purpose: they answer the question "is this build fundamentally broken?" as quickly as possible.

What Smoke Tests Cover

Smoke tests target the critical path of an application. For a web application, this might mean verifying that the homepage loads, the login flow works, and the primary API endpoint responds. They are intentionally limited in scope — the goal is speed and confidence, not exhaustive coverage. A smoke test suite typically runs in seconds or low minutes.

Where Smoke Tests Fit in CI

Smoke tests are most valuable as the first stage in a CI pipeline. If the smoke suite fails, there is no point running hundreds of unit tests, integration tests, or end-to-end tests. This fail-fast approach saves compute resources and gives developers rapid feedback. Many teams also run smoke tests against production after a deploy to catch environment-specific issues immediately.

Smoke Tests vs. Other Test Types

Compared to regression tests, smoke tests cover fewer scenarios and are not concerned with verifying that previous bugs remain fixed. Compared to end-to-end tests, they are lighter — they may skip complex multi-step workflows in favor of simple happy-path checks. Think of smoke tests as a gate: they do not prove the software is correct, but they do prove it is not obviously broken.

Best Practices

Keep smoke tests deterministic and fast. Avoid tests that depend on external services unless absolutely necessary. Tag or group them so they can be triggered independently from the rest of the suite. Monitor their execution time — if smoke tests become slow, they lose their primary advantage as an early warning system.