

Smoke Testing | Sanity Testing |
The main objective of Smoke testing is to verify the stability of the entire system | The main objective of Sanity testing is to verify the rationality of the system |
Smoke testing is executed to ensure that the basic functionalities are working as expected | Sanity testing is executed to verify that the new functionality or the bug fixes are working as expected |
Smoke testing is wide and shallow approach | Sanity testing is narrow and deep approach |
Smoke testing is usually scripted or documented | Sanity testing is usually unscripted |
Smoke testing is performed by the testers and it can also be performed by the developers | Sanity testing is usually performed by the testers |
Smoke testing is like general health checkup of the software | Sanity testing is like a specialized health checkup of the software |
Smoke testing is performed earlier | Whereas sanity testing is performed after the Smoke testing |