The literature on the issue of Sanity vs. Smoke Testing is still not well developed. Accordingly, in this blog, we shall try to take up a comparative analysis of Sanity Testing vs. Smoke Testing. We will look at the differences between the two as well as try to understand their relation with Regression Testing, under the issue of Smoke Testing vs. Sanity Testing vs. Regression Testing.
Whenever, the testing team receives a new Software Build, after minor changes in its functionality or code; Sanity Testing is performed in order to make sure that the bugs have been fixed, all errors have been addressed and there is no addition of new defects. It is a broad, quick and shallow Software Testing Course technique, which helps in evaluating the feasibility of further testing. Sanity Testing is critical in ensuring that the new code changes do not affect the existing functionalities. Sanity Testing is considered to be a variant of Regression Testing and is also known as ‘Cursory Testing’.
