Smoke Testing vs Sanity Testing : A comparison
by Webomates Inc Test Automation Company
Software development and testing are an ecosystem that works on the collective efforts of developers and testers. Every new addition or modification to the application has to be carefully tested before it is released to the customers or end-users. In order to have a robust, secure, and fully functional end application, it has to undergo a series of tests. There are multiple testing techniques involved in the whole process, however, Smoke and Sanity are the first ones to be planned.
Let us examine Smoke Testing vs Sanity Testing in this article.
Smoke testing essentially checks for the stability of a software build. It can be deemed as a preliminary check before the build goes for testing.
Sanity testing is performed after a stable build is received and testing has been performed. It can be deemed as a post-build check, to make sure that all bugs have been fixed. It also makes sure that all functionalities are working as per the expectations.
Let us first take a quick look at the details of both types of testing, and then we can move onto identifying the differences between them. There is a thin line between them, and people tend to confuse one for another.
What is smoke testing?
Smoke testing, also known as build verification testing, is performed on initial builds before they are released for extensive testing. The idea is to net issues, if any, in the preliminary stages so that the QA team gets a stable build for testing, thus saving a significant amount of effort and time spent by the QA.
Smoke testing is non-exhaustive and focuses on testing the workflow of the software by testing its critical functionalities. The test cases for smoke testing can be picked up from an existing set of test cases. The build is marked rejected in case it fails the smoke tests.
Smoke tests can be either manual or automated.
What is sanity testing?
Sanity testing is performed on a stable build which represents minor changes in code/functionality to ensure that none of the existing functionality is broken due to the changes. For this, a subset of regression tests is conducted on the build. Read More about : smoke testing vs sanity testing
If this has picked your interest and you want to know more, then please click here and schedule a demo, or reach out to us at email@example.com. We have more exciting articles coming up every week.
Stay tuned and like/follow us at
Created on Nov 21st 2021 20:42. Viewed 135 times.