Smoke Testing vs Sanity Testing

1. Smoke Testing vs Sanity Testing Let us examine Smoke and Sanity testing - 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. Read More about Smoke Testing vs Sanity Testing

2. 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.

3. 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.  Note that, it is just a check measure in the testing process, and in no way, it replaces comprehensive testing.  Smoke tests can be either manual or automated.

4. What is sanity testing? Sanity testingis 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.

5. You must be wondering why are we even comparing these two when on a superficial level, both of them are performing tests before the “big” testing cycle commences. It may be noted that they are different at many levels, albeit they appear to be similar. Smoke testing takes care of build stability before any other comprehensive testing (including sanity testing) can be performed. It is the first measure that should be ideally taken in the software testing cycle because conducting testing on an unstable build is a plain waste of resources in terms of time, effort, and money. However, smoke testing is not limited to just the beginning of the cycle. It is an entry pass for every new phase of testing. It can be done at the Integration level, system-level, or acceptance level too. Whereas, sanity testing is performed on a stable build, which has passed the acid test of smoke tests and another testing.  Both can be performed either manually or with the help of automation tools. In some cases, where time is of the essence, sanity tests can be combined with smoke tests. So, it is natural for the developers/testers to often end up using these terms interchangeably. So, it is important to understand the difference between the two to ensure that no loopholes are left in the testing process due to this confusion. To summarize, smoke tests can be deemed as general and overall health check-up of the application, whereas sanity tests focus is more targeted health check-u Is it sane to compare Smoke to Sanity testing?

6. Thank You Email address marketingwebomates05@gmail.com Website address https://www.webomates.com/