What is Smoke Testing?

Definition

Smoke testing is a quick, shallow set of checks run on a new build or deployment to confirm that the most important functions work, such as the application starting, users signing in and key pages loading, before deeper testing or release continues.

Importance

A broken build that enters a full test cycle wastes hours of testing effort, and a broken deployment that reaches users causes an outage a few minutes of checking would have caught. Smoke testing is the least expensive gate in a release process: it runs fast, gives a clear pass or fail, and stops obviously broken software before anyone spends more time on it. Run after every production deployment, it also confirms that the release works in the live environment, where configuration and infrastructure differ from staging.

Application

A useful smoke suite is small and stable: a handful of critical paths, such as sign-in, main navigation and one core transaction, automated so it runs immediately after each build or deployment. If a check fails, the build is rejected or the deployment is rolled back before further testing or users are affected. In our ReleaseRhino managed service, the two checks have separate jobs. Smoke tests run in the production environment straight after a deployment, confirming the release went out cleanly and the critical paths still work. The fuller regression suite runs after every release to staging, before anything reaches production. Any smoke failure is logged and reported at once, so the team can fix the problem or roll back while the impact is still small.