Difference between sanity and smoke test

**trainee_tester** · 03-05-2008

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

**vijenjoy2k2** · 05-31-2007

who do the Sanity testing and smoke testing. Tester or Developer.

**sutnarcha** · 05-31-2007

It can be done by either Testers or the Developers.

It depends from company to company and their decision.

But, generally Testers do it.

**ruchikak** · 06-05-2007

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 ?

**jainbrijesh** · 06-05-2007

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.

**ruchikak** · 06-06-2007

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

**jainbrijesh** · 06-06-2007

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.

**ruchikak** · 06-06-2007

Thanks
Congrats for being member of month .

**sridharrganesan** · 10-16-2007

Smoke test and Sanity test almost shares the same definition, but still has some minor differences.

Both Smoke and sanity test are called as Build verification test, and done at the beginning once when the build or application is deployed, and checks whether all the main functionalities are working fine.

The difference is in the smoke test we will be validating the main functionalities only with the positive scenarios, but in the sanity test the main functionalities are validated with both the negative and positive scenarios.

**mwhel** · 02-24-2008

Smoke tests are often scripted where the machine determines whether the outcome was as expected, whereas sanity test are often a gut-check of whether the results "appear" to be reasonable.

**quality_quantity** · 02-25-2008

Smoke testing originated in the hardware testing practice of turning on a new piece of hardware for the first time and considering it a success if it does not catch fire and smoke. In software industry, smoke testing is a shallow and wide approach whereby all areas of the application without getting into too deep, is tested.

A sanity test is a narrow regression test that focuses on one or a few areas of functionality. Sanity testing is usually narrow and deep.

**Tina Mahajan** · 03-18-2008

Hi Dibya,

A smoke test determines whether it is possible to continue testing and
sanity test determines whether it is reasonable to proceed with further testing.

A software smoke test determines whether the program launches and the interfaces are accessible and responsible.
Sanity test exercises the smallest subset of application functions needed to determine whether the application logic functional and correct.

If the smoke test fails, it is impossible to conduct a sanity test.
If the sanity test fails, it is not reasonable to attempt more rigorous testing.

Hope this make it a lot clearer.
Feel free to get back incase of doubts.

Regards,
Tina.

**anilkumar18** · 03-19-2008

Smoke Testing for every Build and Sanity for every Release

Thread: Difference between sanity and smoke test

Thread Tools

Display

Hybrid View

Re: Difference between sanity and smoke test

sanity/smoke testing

Re: sanity/smoke testing

Re: Difference between sanity and smoke test

Re: Difference between sanity and smoke test

Re: Difference between sanity and smoke test

Re: Difference between sanity and smoke test

Re: Difference between sanity and smoke test

Re: Difference between sanity and smoke test

Re: Difference between sanity and smoke test

Re: Difference between sanity and smoke test

Re: Difference between sanity and smoke test

Re: Difference between sanity and smoke test

Posting Permissions

About us

GeekInterview

Interact