Thread: Difference between sanity and smoke test

It can be done by either Testers or the Developers.

It depends from company to company and their decision.

But, generally Testers do it.

Sanity Testing is performed whenever cursory testing is sufficient to provide the application is functioning according to specifications. Thes level of testing is a subset of Regression Testing.

Smoke Testing is a relatively simple check to see whether the product "smokes" when it runs. Smoke Testing is also known as AD-HOC TESTING, e.i. Testing without a formal Test Plan.

Smoke Test a phrase used to describe a subset of tests typically limited in number that can be run against each software build to determine whether the software has regressed in form or function since a previous build.

“Smoke Testing might be a characterized as a rolling integration strategy”. Smoke testing is an integration testing approach that is commonly used when “shrink-wrapped” software products are being developed. It is designed as a pacing mechanism for time-critical projects, allowing the software team to assess its project on a frequent basis.

The Smoke Test should exercise the entire system from end to end.
Smoke Testing provides benefits such as:

1) integration risk is minimized.
2) the quality of the end-product is improved.
3) error diagnosis and correction are simplified.
4) progress is easier to asses.

Sanity Testing - typically an initial testing effort to determine if a new software version is performing well enough to accept it for a major testing effort.
For example, if the new software is often crashing systems, bogging down systems to a crawl, or destroying databases, the software may not be in a 'sane' enough condition to warrant further testing in its current state.

Originally Posted by ruchikak

After so much discussion , I am still not able to comprehend the difference between these two types of testing.
Anyone please answer in points.
a) Is sanity and smoke testing same? say yes or no
b) If no then what is the basic difference ?

sanity and smoke testing are not same.

Difference can be better understand with this example.

If you purchase a new mobile and you use it with care for few days, this is sanity testing.You will see, ya, all functions are well working.Now after few days it's on to you how badly you use/test it.

Now you have added memory card in your mobile, or have purchased handfree for your mobile which was not there.Now you will see whether memory card or handfree kit is working with your cell or not?this is smoke testing.

I hope now it should be clear to you and there should be no confusion.

Originally Posted by ruchikak

Thanks Brijesh.
On the basis of ur example can u please define these two types of testing . That will help.

Sanity testing is initial testing to verify that the build is working and exhaustive testing can be performed.

Smoke testing is required when any new feature or function is added in the existing working build to verify that the build is still working with new feature added.

Smoke testing:

is it possible to test the application/software further,this type of testing is done with minimum requirements and decision whether further testing is possible or not is taking immediately...

Sanity testing:

is it resonable to test the application/software, once smoke testing is done sanity testing is performed ,and decision of whether testing the application/software is resonably is taken immediately.

Both type of testing is done with minimum requirements~~`

Both sanity tests and smoke tests are ways to avoid wasting time and effort by quickly determining whether an application is too flawed to merit any rigorous testing.


thanks & regards
trainee_tester