Smoke Testing -
Smoke Testing is performed after software build received, this is performed to find out that the critical functionalities of the program is working fine.
It is performed “before” any detailed functional or regression testing on the software build.
The purpose of this testing is to discard any broken application, so that the QA team does involve and waste time in installing and testing the software application.In this, the test cases selected cover the important functionality of the system. The objective is not to perform in-depth testing, but to verify if the critical functionalities of the system are working fine.
Sanity Testing
Sanity testing is performed after receiving a software build, with minor changes in code, or functionality, to confirm that the bugs have been fixed and there are no further issues introduced due to the new changes. The objective is to determine that the recommended functionality works as expected. If the test fails, the build is rejected to save the time and costs involved in a more severe testing.
