When do you perform smoke testing and Sanity Testing

Question

I would like to know when you perform smoke testing and sanity testing?

Answer 1

Smoke Testing: Is usually perforformed before passing on build to testing team. Smoke Testing is performed to make sure that build is stable enough to be tested.

Sanity Testing: is usually performed to make sure that bugs/ user stories are sucessfully working in build. Sanity Testing is performed usually before UAT and Regression.

 

Both smoke testign and sanity testing are used to save testing team's time.

Answer 2

A smoke test is done to make sure if the build we received from the development team is testable or not whereas the Sanity Test is done during the release phase to check for the main functionalities of the application without going deeper.


When to perform smoke testing?
Smoke testing is done on initial builds. It is a part of basic testing. Usually done every time there is a new build release.

When to perform sanity testing?
Sanity Testing is done on stable builds. It is a part of regression testing. It is planned when there is no enough time to do in-depth testing.


There are many tools available for automation which does not require prior training for language. One such tool is called QAppAssure. It simplifies integration with Jenkins/JIRA/Slack/TestRail and acts as an integrated test case management module to assist in managing a firm’s testing teams. It provides both APIs and UI options to integrate QAppAssure with CI/CD tools, issue management portal, test case management portal, and messaging channels and raise pre-configured bugs report directly from the portal.