2

This question already has an answer here:

I am new to "Manual Testing". Just wanted to know the difference between Smoke Testing and Sanity Testing with software examples for better understanding.

marked as duplicate by Niels van Reijmersdal, Kate Paulk, Lyndon Vrooman, Dhiman, Bruce McLeod Aug 13 '15 at 1:47

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

1

Smoke Testing : After a new build, Smoke testing an application means checking that the critical functions of the application still work. Smoke testing is done to reject any badly broken software.

The main idea behind this test is that if the primary application functionality is not working, then there is no point carrying on further testing.

For example, a typical smoke test for a web application would be that is launches successfully. If the web application returns a 404 error or fails to lunch, then there is no point in testing anything further. We need to fix the bugs so that the primary functions work.

Sanity Testing : After receiving a build with minor changes in the code or functionality, a subset of regression test cases are executed that to check whether it rectified the software bugs or issues and no other software bug is introduced by the changes.

The objective is not to verify the new functionality, but to verify that the developer has applied some rationality or 'sanity' while fixing the bug.

You'll find a lot of good links if you search on Google, where you can find a much detailed description. Here are two such links : Link1, Link2

Not the answer you're looking for? Browse other questions tagged or ask your own question.