冒烟测试是一种测试，用于确保程序的急性功能正常工作。它也被称为验收测试的子集，用于测试系统/产品的所有函数。另一方面，进行健全性测试以检查构建后是否已修复错误。它也被称为回归测试的子集。
烟雾测试和健全性测试存在混淆，因为这两种类型的测试是相同的，但烟雾测试和健全性测试都有自己的目标和优先级。因此，在这篇文章中，我们将展示冒烟测试和健全性测试之间的区别。
下面是详细对比
| 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. |