|
Answer» SMOKE Testing: It is a type of testing performed to ensure that the acute functionalities of the program are working well. It acts as a confirmation of whether the QUALITY assurance team can further proceed with testing or not.
Sanity Testing: It is an unscripted form of testing performed to ensure that the code changes that are made are working well. It is performed by the test team for some basic tests. This testing focuses on ONE or a few areas of functionality and is usually narrow and deep.
Smoke vs Sanity Testing: | Smoke Testing | Sanity Testing |
|---|
| Its main objective is to measure the stability of the system so that the team can proceed with more rigorous testing. | Its main objective is to measure the rationality of the system so that the team can proceed with more rigorous testing. | | It is usually performed by the developers or testers. | It is usually performed by testers. | | It is a subset of regression testing. | It is a subset of acceptance testing. | | It can be executed both manually or by using automation tools. | It can only be executed manually, not by using automation tools. | | It is generally performed when a new product is developed. | It is generally performed after regression testing. | | It is documented and is used to test the end-to-end FUNCTIONS of the application. | It is not documented and is used to test only modified or defect-fixed functions. | | It is ALSO considered as a subset of acceptance testing. | It is also considered a subset of regression testing. |
|
