Smoke Testing is a type of testing which is done to assure that the acute functionalities of program is working fine. It is also known as subset of acceptance testing and it is used to test all over 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 subset of regression testing.
There is confusion with smoke testing and sanity testing that these two type of testings are 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
|Smoke Testing||Sanity Testing|
|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.|
|Smoke testing is also called subset of acceptance testing.||Sanity testing is also called subset of regression testing.|
|Smoke testing is documented.||Sanity testing isn’t documented.|
|Smoke testing is performed by either developers or testers.||Sanity testing is normally performed by testers.|
|Smoke testing may be stable or unstable.||Sanity testing is stable.|
|Smoke testing is scripted.||Sanity testing is usually not scripted.|
|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.|
|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.|
|Smoke testing can be performed either manually or by using automation tools.||Sanity testing is commonly executed manually, not by using any automation approach.|
|Smoke testing is performed when new product is built.||Sanity testing is conducted after the completion of regression testing.|