Smoke testing vs Sanity testing

Most of the peoples have misconception for these two testing as the difference between the two is very slick and one can get easily confused with one another.

Let us discuss bot the types of testing in detailed manner and difference between them. 

Smoke Testing:

This is a type of testing in which tester checks for major and critical functionalities that they are working correctly or not

This is performed for the identification of any blocker or critical bug that may lead to wastage of valuable testing time divided and allocated for different functionalities

Sanity testing: 

This is the type of testing where tester tests new functionalities and minute or minor changes in the previous functionalities provided these minor changes do not have impact on any other dependent functionality

This is performed to verify that all previous functionalities are working almost as expected and if this test case comes up with a fail result then further testing will not be continued as basic functionalities are only not working.

When these two are performed:

Smoke testing is tested at various levels like the developer does it to test build success status, testers perform it before testing every build and at the client side, it will be performed as pre-acceptance testing.

Whereas, sanity testing is performed in the final builds by the testers to test minor changes has not affected the basic functionalities and all previous functionalities are working as they should do.

Pictorial representation will make it more clear

Limelight on the differences between two:

1. Smoke is to test the critical and major ones are working fine whereas sanity is to test newly added modules and resolved bugs with minor changes
2. Smoke is to test stability at a glance but on the another hand sanity tests for rationality between modules
3. Scripted and documented steps are taken for smoke but nothing is documented for sanity
4. Smoke can be said as small part for regression and sanity can be said as a part of acceptance testing
5. Entire end to end testing is performed in smoke but in sanity, particular modules are being tested

Conclusively, it can be said that both of them are performed to save time so that valuable time can be saved and a more reliable and the quality product comes up at last.

Thanks