# Smoke Testing

Smoke testing runs a small set of critical checks to determine whether a build or deployment is functional enough for further use or testing.

- Type: method
- Domain: Engineering & architecture
- Level: Foundational
- Last reviewed: 2026-10-19
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/smoke-testing/>)

## What it means

Smoke testing is broad but shallow verification of essential functions after a build, deployment, or environment change. It aims to detect blocking failures quickly, such as an application that cannot start or a critical route that cannot load. It is not a complete regression suite and does not certify a release as defect-free.

## Why it matters

When a basic dependency or configuration is broken, deeper testing produces noise and wastes time. A short initial check gives teams fast feedback on whether the environment is usable and whether investigation should begin immediately.

## When to use it

Use it as an early pipeline gate or a controlled post-deployment check. Select safe, important operations and dedicated test data. Do not exercise real irreversible customer transactions merely to prove a system is reachable.

## How it works

1. Choose a minimal set of critical paths and observable success conditions.
2. Prepare known test accounts, data, and cleanup behavior.
3. Check startup, important routes, and a representative essential operation.
4. Stop or escalate on failure with useful logs and context.
5. Continue broader verification when smoke checks pass and revise the set as risks change.

## A practical example

After deploying a subscription portal, a smoke check loads sign-in, authenticates a test account, and retrieves its billing summary. A missing environment setting breaks the summary, so rollout pauses before the team spends time on the full regression suite.

## Where it breaks

Smoke tests intentionally leave most states and edge cases unexplored. A passing result does not establish accessibility, security, performance, or overall correctness. Brittle checks can also block healthy releases, so keep them focused and diagnosable.

## Common mistakes

- Calling a successful homepage request proof that critical workflows work.
- Expanding the suite until it loses its fast-feedback purpose.
- Skipping deeper checks because the smoke tests passed.

## Sources

1. [What is Smoke Testing tool?](<https://www.browserstack.com/guide/smoke-testing-tool>) — BrowserStack · Technical guidance
2. [The different types of testing in software](<https://www.atlassian.com/continuous-delivery/software-testing/types-of-software-testing>) — Atlassian · Technical guidance

## Related topics

- [Continuous Delivery](<https://wiki.soroush.uk/topic/continuous-delivery/>)
- [End-to-End Testing](<https://wiki.soroush.uk/topic/end-to-end-testing/>)
- [Regression Testing](<https://wiki.soroush.uk/topic/regression-testing/>)
