Smoke Testing

Smoke testing is a preliminary check that verifies the most critical features of your app are working before investing time in detailed testing. Named after electronics testing where you power on a device to see if smoke appears, smoke tests answer the basic question: “Is the app fundamentally broken or can we proceed with testing?” These quick tests typically check essential functions like app launch, login, navigation, and key workflows.

Development teams run smoke tests after deploying new code to verify the build is stable enough for further testing. If smoke tests fail, there’s no point running comprehensive test suites—the build needs fixing first. Smoke tests are designed to run fast, often completing in minutes, so teams get immediate feedback on whether a build is worth testing or should be rejected immediately. This saves time by catching catastrophic failures early.

For businesses, smoke testing provides an early warning system that prevents obviously broken apps from reaching testers or users. When your development team deploys an update, smoke tests immediately verify that core functionality still works. This is especially valuable for continuous deployment pipelines where code is deployed frequently—smoke tests gate each deployment, ensuring that only builds passing basic sanity checks reach production servers or app stores.