Smoke Testing: is use to find issues in the early phases of testing and is performed after software build to discover that the critical functionalities of the program is working fine. It is executed “before” any detailed functional or regression tests are executed on the software build. The smoke testing is performed by testers after every build is received for checking whether the build is in testable condition or not.
Sanity Testing: After receiving a software build, with minor or some changes in code, or functionality, Sanity testing is performed to check that the bugs have been fixed and no further issues are introduced due to these changes. The goal is to determine that the proposed functionality works roughly as expected. If sanity test fails, the build is rejected to save the time and costs involved in a more rigorous testing.
Difference between Smoke testing and Sanity testing
1. Smoke testing is performed to ascertain that the critical functionalities of the program are working fine.
Sanity testing is done to check the new functionality/ bugs have been fixed.
2. The objective of this testing is to verify the “stability” of the system in order to proceed with more rigorous testing.
The objective of the testing is to verify the “rationality” of the system in order to proceed with more rigorous testing.
3. This testing is performed by the developers or testers.
Sanity testing is usually performed by testers.
4. Smoke testing is usually documented or scripted.
Sanity testing is usually not documented and is unscripted.
5. Smoke testing is a subset of Regression testing.
Sanity testing is a subset of Acceptance testing.
6. Smoke testing exercises the entire system from end to end.
Sanity testing exercises only the particular component of the entire system.
7. Smoke testing is like general health check up.
Sanity testing is like specialized health check up.