Smoke testing-

It is basically building validation. Smoke Testing is performed after software in built to ascertain that the critical functionalities of the program are working fine. It is done after the built of the application is done. Basic check is done on the application. To see if the built that happened are we accepting it or not. We will randomly choose some functionality and see if they are working or not. We will navigate to 3, 4 pages of a web application to see if build is stable. It is usually done within 5-10 minutes after the build happened to see that application does not break. After doing smoke testing we will go to do more elaborate functional testing.

Sanity Testing-Sanity testing is performed to ascertain that bugs are fixed to check no further issues are introduced to these changes. It is done once application is fully stable.

Lets take an example

After 40-50 builds after all bugs are fixed the only bug remaining is we can’t tag someone in photos. So after the developer touches that image code and tries to fix the tag bug he may change some other changes to picture code. I.e. some other functionality changes now. Example we can tag photos now but can’t download photos.

So to check if fixing of one defect, doesn’t do additional changes in functionality of code We have to test other functionality as well. So this type of testing is called sanity testing.