Smoke Testing
• Smoke testing is the initial testing process exercised to check whether the software under test is ready/stable for further testing.
• The Smoke testing is typically executed by testers after every build is received for checking the build is in testable condition.
• These test cases are executed prior to start actual testing to check critical functionalities of the program is working fine.
• Smoke testing follows shallow and wide approach where you cover all the basic functionality of the software.
• The test cases can be executed manually or automated; this depends upon the project requirements.
• Smoke Testing, also known as “Build Verification Testing”.
Sanity Testing
• Sanity testing to check the after minor fixes the small section of code or functionality is working as expected & not breaking related functionality.
• The main aim of Sanity testing to check the planned functionality is working as expected.
• Sanity testing follows narrow and deep approach with detailed testing of some limited features.
• Sometimes it is the part of Regression Testing