📅 最后修改于: 2021-01-11 01:59:43 🧑 作者: Mango
| S.No. | Smoke Testing | Sanity Testing |
|---|---|---|
| 1 | It is a broad approach to testing where all parts of the application are tested. | It is a narrow approach to testing where specific parts of the application are tested. |
| 2 | It measures the stability of the system by performing rigorous testing. | It measures the rationality of the system by performing rigorous testing. |
| 3 | Smoke testing can be either manual or automated. | Sanity testing can be done without test cases or scripts. |
| 4 | It is performed by both testers and developers. | It is performed by only testers. |
| 5 | Testing is done without getting into deep but whenever needed tester has to go into deep. | Sanity testing does not need to go into deep of the application. |
| 6 | Smoke testing is documented. | Sanity testing is not documented. |
| 7 | It is used to test End to End function of the application. | It is used to test only modified or defect fixed functions. |
| 8 | It is considered as a subset of acceptance testing. | It is considered as a subset of regression testing. |