Sanity Testing VS Smoke Testing Diffrance with information

Introduction

 

The life of a QA Tester will be considered incomplete if the terms ‘Smoke Testing’, ‘Sanity Testing’ and ‘Regression Testing’ are not infused into it. Though these are some regularly used terms, there are some common misconceptions around them too.

 

Software Build

Before we delve deeper into how these three testing methods differ, we must explain what a software build is.

Can you think of the primary component of building software? Well, yes, we are talking about the code. But we know that it is not just one code that builds the entire software. There are thousands of source code files depending on the complexity of the software. Needless to mention, these source codes need to be compiled into a single executable file, which can be shared with the release team to be deployed. The process of compiling these source code files into a single file is called a software build. It is pretty literal here because it is the process where the software is built to implement it.

 

Smoke Testing	Sanity Testing
Smoke Testing is performed to ascertain that the critical functionalities of the program is working fine	Sanity test is done to check the new functionality /bugs have been fixed
This testing is performed by developer or tester	This testing is performed by tester
Sanity testing exercises only the particular component of the entire system	Smoke testing exercises the entire system from end to end
To test the stability of new build	To test the stability of new functionality or code changes in the existing build
It is a part of basic testing	It is a part of regression testing
Smoke testing , build may be either stable or unstable	Sanity testing , build is relatively stable