Sanity Testing is used to check whether it is REASONABLE to 
carry out further testing or not whereas Smoke testing 
checks whether its POSSIBLE to carry out the testing.An 
ideal sanity test exercises the smallest subset of the 
application functions needed to determine whether the 
application logic is functional & correct whereas in smoke 
testing the tester touches all areas of application without 
going deep. eg. interest calculation of a financial 
application is sanity testing.On the other hand tests like 
can i open the page or is a button on the page working 
properly are examples of Smoke testing.

Sanity testing is done by developers only i think. If it's
wrong, correct me please..

Hi,
 This is sneha.

No it is done only by the testers not developers

Both Smoke Testing and Sanity Testing are initial, non
detailed, quick testings performed on an application to
check if All the windows/ features/ objects are basically
available to carry-on the detail testing on the application. 

The difference between Smoke testing and Sanity testing is
that practically both are same but perceptually they are
different. I mean Smoke testing is done with negative
perception like assuming as application may fail or throw an
exception/ error or may crash etc. whereas Sanity testing is
done with positive perception.

In Smoke Testing you can check Stability of Build as well 
as is it ok for further testing or not.
In sanity Testing,you can check whether build rectifies all 
issues, and no issue is left.Sanity Testing is a Subset of 
Regression Testing.

SMOKE TESTING IS DONE BY DEVELOPERS FOR FURTHER 
PROCESS,TETING.

SANITY TESTING IS DONE BY TEST ENGINEERS FOR CHECKING THE 
BUILD IS TESTABLE OR NOT.

smoke testing: After getting every build we r doing smoke
testing. smoke testing test the basic functionality of the
application. if smoke test fails no need to do further
testing .As a tester we should reject that build and send to
the dev
Sanity Testing: It check the healthiness of the
application.In this testing we check wether the build is
working properly or not.No issue should be left
 Both are done by tester

sanity and smoke testing both is  Done By Plumber Neither
Developer Nor By Tester

SMOKE Testing - When a tester get build from the Dev, 
tester perform the initial testing to ensure that the basic 
functionality is working fine or not. If not then further 
detail testing is not proceeded. This initial testing 
before the detail testing is known as SMOKE testing.

Sanity Testing - Once the all the test cycles have been 
executed and all the open defects have been fixed and 
retested, now before providing the signoff for next phase 
testers needs to do Sanity testing to test some critical 
functionality which will ensure that the defect fixes have 
not disturb the other functionality. This test cycle is 
short and quick and is known as Sanity testing.

There is no difference between smoke testing and sanity 
testing. smoke testing is also know as sanity testing.

Smoke testing me testing the basic and critical feature of 
the application before doing the regress testing.

Smoke testing is always done by the Testers. Not by the 
developer.

There is no difference between Smoke and Sanity testing,
both testing will be done when we will get a new build and 
to test whether further it is testable or not.

But the only difference is in sanity testing first we need 
to test whether last build test cases are working fine or 
not, bcs when we get new build some time it should not 
support the last build test cases.