Sanity and Smoke Testing

Nathen — Fri, 19 Mar 2010 16:12:47 -0600

In a perfect world, software and websites would be fully linguistically and functionally tested any time a change is made. Realistically, cost efficiency needs to determine the testing scope. Smoke tests and sanity tests give your software a cursory check when the risk/benefit does not justify the costs of deeper testing.

Whereas sanity testing is a targeted form of regression on a specific scope, smoke testing is broad and shallow to touch the entire application. Both of these quick, limited tests can be executed to idenitfy showstopping bugs before moving to the next phase of the project. Neither are exhaustive but are capable of exposing critical issues. These tests are especially crucial before a more costly testing effort is executed on a bad build.

For safety and customer satisfaction, full testing is critical. When these can be assured for minor changes, a carefully designed smoke or sanity test is a less costly option to assure the best quality and return on investment.

Posted to: Sanity and Smoke Testing Show Thread | Post Reply

Forum posts to 'Quality and Safety'

Sanity and Smoke Testing