Smoke testing
Smoke testing is also known as "build verification" testing. It is performed right after the testing team receives the build. The functionality covered by the smoke tests are crucial, failing of which results in rejection of build. In short, we will execute the most crucial tests to make sure that the application can be considered suitable for further exhaustive testing or not.
Example- Smoke tests for some application like GMail will include test cases that are very critical to the app e.g. user should be able to login to the application, inbox should be populated with recieved mails, user should be able to send mail etc.
Example- Smoke tests for some application like GMail will include test cases that are very critical to the app e.g. user should be able to login to the application, inbox should be populated with recieved mails, user should be able to send mail etc.
Sanity testing
Sanity testing is the subset of regression testing. Like regression, in case of sanity testing, we check if a fix has not affected the other working functionalities of the application but in a lesser time and with lesser number of test cases.
So, basically we perform sanity testing after receiving a fix (usually a minor fix). We check limited but critical part of functionality and then decide as to whether further testing is required or not.
So, basically we perform sanity testing after receiving a fix (usually a minor fix). We check limited but critical part of functionality and then decide as to whether further testing is required or not.
