Actually there is no differents between SMOKE TESTING &
SANATY TESTING..... both are similar

Deff:  SMOKE TESTING/SANITY TESTING:

                              Before Testing an Application,
tester should install d developed application in his
computer and check if it is working or not ,, i.e without
using any test techniques. If it is working right then the
application should be accepted for testing with using the
prior test techniques...

Sanity testing - Checking the initial build 
roughly....whether all the windows or pages are working or 
not...just a rough check of the build.

Smoke testing - checking the build by entering some values 
for that...

Sanity  + smoke testing is called - Tester acceptance 
testing.

Usually tester performs these tests and if build is 
suceeded then he will accept the build and will start the 
testing process.

Kumar.rnv@gmail.com
Broadridge.

Sanity Testing - Testing the build is in the sane 
(position) of testing or not.
Sanity testing is carried out by Test Lear or Tester before 
starting actual detailed testing of the new build. In other 
words we can say that deciding whether to accept the build 
for testing or not.

Smoke Testing - Testing of application without following 
any pattern. Smoke testing is generally done by Project 
Lead / Project Manager or Client - just to check whether 
all major features are working properly or not.

Note : Sanity Testing and Smoke Testing are totally 
different terms and are not same.

Smoke testing : Testing the build to ensure that further
testing can be proceed 

Sanity Testing : Testing part of application for which bug
fixing has done.Also checking the bug fixing related
modules.This is a subset of regression testing

Smoke testing:In simple terms we can say that checking the
application whether complete functionalities are covered or
not in order to perform detailed testing on the application

Santiy Testing:In simple terms we can say that,checking the
application whether it is stable or not   (OR) checking
behaviour of the application.here we are not performing any
functionality testing.We just looking whether the
application is moving softly without any interruption.

I hope u cleared.

Hi 

Smoke Testing - Once new build is submitted to testers for 
testing, testers usually perform smoke test on new build in 
order to verify if build is acceptable for further testing. 
In smoke testing, you are not bothered about functionality 
but things like none of the links are broken, no page is 
displaying Error-404 (web based application) and 
application is in stable state.

Sanity Testing - Once Testing team is done with their all 
levels of testing and ready to submit the application for 
production, testers usually perform sanity tests before 
submitting application to production. In sanity testing you 
perform full testing to ensure that nothing has been left 
out. Sanity check is done taking into consideration all 
functional, integration and regression test cases.

Regards
Anand