In this article, we see what is Smoke Testing and Sanity Testing and also the difference between Smoke and Sanity Testing. Both smoke tests and sanity tests have their own objectives and priorities. These two types of testing play a key role in the success of a project.
Smoke and Sanity Testing come into the picture after build release. Many testers who are in the starting stage of the career feel it as a chaos. Here in this article, let’s see what Smoke and Sanity Testing are and the difference between Smoke and Sanity Testing in detail with practical examples to understand easily.
Check below video to see “Smoke Testing Vs Sanity Testing”
Please be patient. The video will load in some time.
If you liked this video, then please subscribe to our YouTube Channel for more video tutorials.
What is Smoke Testing in Software Testing:
Smoke Testing is done to make sure if the build we received from the development team is testable or not. It is also called as “Day 0” check. It is done at the “build level”.
It helps not to waste the testing time to simply testing the whole application when the key features don’t work or the key bugs have not been fixed yet.
What is Sanity Testing in Software Testing:
Sanity Testing is done during the release phase to check for the main functionalities of the application without going deeper. It is also called as a subset of Regression testing. It is done at the “release level”.
At times due to release time constraints rigorous regression testing can’t be done to the build, sanity testing does that part by checking main functionalities.
Earlier I have posted a detailed post on “Difference between Regression and Retesting”. If you haven’t gone through it, you can browse by clicking on the link.
Smoke Testing Vs Sanity Testing
Example to showcase the difference between Smoke and Sanity Testing:
For example: In a project for the first release, Development team releases the build for testing and the test team tests the build. Testing the build for the very first time is to accept or reject the build. This we call it as Smoke Testing. If the test team accepts the build then that particular build goes for further testing. Imagine the build has 3 modules namely Login, Admin, Employee. The test team tests the main functionalities of the application without going deeper. This we call it as Sanity Testing.
Some more differences between Smoke Testing and Sanity Testing:
- Smoke Test is done to make sure if the build we received from the development team is testable or not.
- Sanity Test is done during the release phase to check for the main functionalities of the application without going deeper.
- Smoke Testing is performed by both Developers and Testers.
- Sanity Testing is performed by Testers alone.
- Smoke Testing exercises the entire application from end to end.
- Sanity Testing exercises only the particular component of the entire application.
- Smoke Testing, build may be either stable or unstable.
- Sanity Testing, build is relatively stable.
- Testing Complete Tutorial
- 100+ Types of Testing Every Tester Should Know
- Manual Testing Interview Questions
- QA Interview Questions