Smoke and Sanity Testing

Sanity Testing

Sanity testing is performed after receiving software build to verify that all major functionalities are working as expected. If the sanity test fails then build rejected and through this its saves money and time for both client and testing.

Smoke Testing

Smoke testing is the process that we make sure that the software under test is stable enought to proceed testing.  Smoke testing helps us tp find bugs that are introduced while integration of modules.

When Smoke Testing Performed?

Smoke testing is usually performed when initial release of module comes. We check system major functionalities are working properly and there is not any issue enough to declare build is not stable. Although at the initial stage build is not stable but when tester found issues then raise it and developer fixes it and after that build becomes stable.

When Sanity Testing Performed?

After its declared that build is stable then there is very least chances of test cases to fail so when at that time we conduct testing is called Sanity.