Skip to content
Related Articles

Related Articles

Software Engineering | Differences between Sanity Testing and Smoke Testing

View Discussion
Improve Article
Save Article
  • Last Updated : 15 Sep, 2022
View Discussion
Improve Article
Save Article

Smoke Testing is a type of testing which is done to assure that the acute functionalities of the program is working fine. It is also known as a subset of acceptance testing and it is used to test all over the function of the system/product. on the other hand 

Sanity Testing is done to check the bugs have been fixed after the build. and it is also known as a subset of regression testing. There is confusion between smoke testing and sanity testing that these two types of testing are the same, but both smoke testing and sanity testing have their own objectives and priorities. So, 

Here in this post, we will show the difference between Smoke Testing and Sanity Testing. Below is a detailed comparison:

S. No.Smoke TestingSanity Testing
1.Smoke testing is done to assure that the acute functionalities of program is working fine. Sanity testing is done to check the bugs have been fixed after the build.
2.Smoke testing is also called subset of acceptance testing. Sanity testing is also called subset of regression testing.
3.Smoke testing is documented.Sanity testing isn’t documented.
4.Smoke testing is performed by either developers or testers.Sanity testing is normally performed by testers.
5.Smoke testing may be stable or unstable.Sanity testing is stable.
6.Smoke testing is scripted.Sanity testing is usually not scripted.
7.Smoke testing is done to measures the stability of the system/product by performing testing.Sanity testing is done to measures the rationality of the system/product by performing testing.
8.Smoke testing is used to test all over function of the system/product.Sanity testing is used in the case of only modified or defect functions of system/products.
9.Smoke testing can be performed either manually or by using automation tools.Sanity testing is commonly executed manually, not by using any automation approach.
10.Smoke testing is performed when new product is built.Sanity testing is conducted after the completion of regression testing.
11.It includes all of the system’s essential basic functionality. It includes only those modules where change in code is made. 
12.Smoke Testing firstly performs on the initial build. smoke testing is done first. Sanity Testing is done on stable builds or for the introduced new features in the software.
13.Smoke testing can be carried out either way-manually or automatically. Without using test cases or scripts sanity testing can be carried out.
14.There is end-to-end system verification done in smoke testing.A specific component gets verified in sanity testing. 
15.In the smoke testing process, the software build could be stable or unstable. During sanity testing, the software build is comparatively stable.
16.For every new build release smoke testing is carried out.Sanity testing is carried out when in-depth testing is not possible because of short time.
My Personal Notes arrow_drop_up
Recommended Articles
Page :

Start Your Coding Journey Now!