Smoke testing : This test only examines the basic functionality of a system to ensure the software works properly (or is not plagued with too many problems) so that the next test can proceed.
Sanity testing : This type of testing is also known as a build-verification test and is usually performed after a smoke test. The testing is performed after a complete software build with minor changes is released to verify that the code changes introduced continue to work as intended.
| Smoke Testing |
Sanity Testing |
| Smoke testing is done to assure that the acute functionalities of the program are working fine. |
After receiving a software build that has undergone minor code or functionality changes, sanity testing is conducted to ensure that bugs have been fixed and that there are no further problems that can be introduced by the changes. |
| It is possible to perform smoke testing manually or with the help of automation tools. |
It is common to perform sanity testing manually, not through automation. |
| Both developers and testers perform smoke testing. |
Testers perform sanity testing. |
| There is documentation or scripting for smoke testing. |
There is no documentation for sanity testing. |
