Difference Between Smoke And Sanity Testing

Replies to This Discussion

Permalink Reply by Lingesh Mukilan on October 19, 2012 at 7:13pm

Smoke testing is like General Health Check Up...

Sanity Testing is like specialized health check up

Smoke testing is performed by the developers or testers

Sanity Testing is done to check the new functionality / bugs have been fixed..

 

• ▶ Reply

Permalink Reply by VJkumran on October 19, 2012 at 7:13pm

sanity also know SMOKE testing is done to check critical functionalities of the system before its is accepted for major testing. Sanity testing is quick and is non- exhaustive. Goal is not to find defects but to check system health.

• ▶ Reply

Permalink Reply by VJkumran on October 19, 2012 at 7:22pm

   

Smoke Testing

1. Smoke testing is done to check the normal health of the build and make sure if it is possible to continue testing. It is done in the beginning of the software testing cycle.
2. A subset of most basic and important test cases is selected and run to make sure that most basic and crucial functions of the software are working fine.
3. It follows shallow and wide approach where you cover all the basic functionality of the software.
4. Smoke test is scripted, i.e you have either manual test cases or automated scripts for it.

5. In some organizations smoke testing is also known as Build Verification Test(BVT) as this ensures that the new build is not broken before starting the actual testing phase.

Sanity Testing 

1. When there are some minor issues with software and a new build is obtained after fixing the issues then instead of doing complete regression testing a sanity is performed on that build. You can say that sanity testing is a subset of regression testing.
2. Sanity testing is done after thorough regression testing is over, it is done to make sure that any defect fixes or changes after regression testing does not break the core functionality of the product. It is done towards the end of the product release phase.
3. Sanity testing follows narrow and deep approach with detailed testing of some limited features.
4. Sanity testing is like doing some specialized testing which is used to find problems in particular functionality.
5. Sanity testing is done with an intent to verify that end user requirements are met on not.
6. Sanity tests are mostly non scripted

Hope it may help you!

Cheers,

 VJ

• ▶ Reply

Permalink Reply by sandeep hanumanthakari on October 19, 2012 at 10:56pm

Simple difference is

Smoke testing is high level testing of build to check nothing has broken.

Sanity testing is same as smoke testing which covers some detail testing than smoke..

• ▶ Reply

Permalink Reply by Kamal on October 22, 2012 at 3:11pm

Smoke testing is Non-Functional Testing and Sanity Testing is Functional Testing.

• ▶ Reply

Permalink Reply by Alligatortek on October 24, 2012 at 9:54am

Hi Supriya,

Sanity Testing:-Tester conducts the Sanity test to ensure the stability of the application build.Tester finds weather the application build is stable for complete application or not.

Smoke Testing:-It covers the major functionality of the application without bothering with finer details.

By,

www.alligatortek.com

• ▶ Reply

Permalink Reply by Anna Trinh Vu on October 26, 2012 at 3:40pm

 You might find it very helpful. :)

source: http://www.guru99.com/smoke-sanity-testing.html

• ▶ Reply