According to Josh Smoke testing :In which the application is tested initially inorder to ensure whether all functionalities are available to perform detail testing on them
sanity testing:In which one can perform testing on an overall application initially to check whether the application is proper in terms of availability and Usability.
sanity testign is also called as Build verification testing. Every Build release from developer should be followed by sanity testing. - In sanity testing we install the application, launch the application and navigate through the application.
- Sanity test is implemented to make sure the application is ready for complete testing.
Every Build release to the client should be preceded by smoke testing. - smoke testing is implemented to make sure the application given to the client on the final release media is working fine, - smoke testing will be a quick test phase to test installation, launching and basic functionality navigation. - smoke testing is carried out using the check lists. -smoke testing is carried out before every release to the client.
Sanity testing is performed whenever cursory testing is sufficient to prove the application is functioning according to specifications. This level of testing is a subset of regression testing. It normally includes a set of core tests of basic GUI functionality to demonstrate connectivity to the database, application servers, printers, etc.