Both the types of testing are done to check whether the 
application is ready for testing and to check its 
stability...
sanity testing:

1.Formal Testing
2.Done at the Entry and Exit stage of each phase of SDLC
3.Usually Done by both Tester/Developer
4.Major / Business Functionalities are focused

smoke testing:

1.Informal testing
2.Done at any point
3.usually done by developers

smoke testing is nothing but whether all options in the 
project are working or not eg menu list ....etc

sanity test ..is the intial testing process ,

sorry,will have to differ a little here.
 Smoke testing is a broad level testingin which all major
functionalities are covered and it is made sure that the
product is ready to be tested.

Sanity testing is a kind of focussed regression testing.. It
is done to make sure that a particular functionality that
had errors before is ready for test.

sanity Testing : Validate the application is well condition 
or not.
Smoke testing: To ensure that appliacation is eligible for 
further testing.

Hi 

In fuctionailitywise no difference between Smoke and Sanity 
Testing.

Smoke testing conducted on new build came for 
testing.purpose is to test stability and future testing 

Sanity testing conducted on Modified build(After fix the 
bugs).

HI,
Sanity Testing means , in some companies they'll do sanity 
testing when the tester recieves a new build they will 
check for stability of the build for further testing.
and in some compnies they'll concentrate on minor changes 
or Particular Bugs (kind of regression testing).

Smoke Tetsing:
In some Companies developers do this tetsing whether the 
build is ready to test.
and in some companies testers will do.
whether the build is stable and checks the major 
functionality of the build.

correct me if im wrong

Sanity Testing:- nothing but testing the functionalities .
Smoke Testing:- nothing but is the software is eligible to 
test also called as Testor Accepetable Test or Eligibility 
Test

sanity Testing : To validate the application whether it is
well in condition or not.
Smoke testing: To ensure that application is eligible for 
further testing.

In software development, the sanity test determines whether 
it is reasonable to proceed with further testing. Software 
sanity tests are commonly conflated with smoke tests. A 
smoke test determines whether it is possible to continue 
testing, as opposed to whether it is reasonable. A software 
smoke test determines whether the program launches and 
whether its interfaces are accessible and responsible (for 
example, the responsiveness of a web page or an input 
button). If the smoke test fails, it is impossible to 
conduct a sanity test. In contrast, the ideal sanity test 
exercises the smallest subset of application functions 
needed to determine whether the application logic is 
generally functional and correct (for example, an interest 
rate calculation for a financial application). If the 
sanity test fails, it is not reasonable to attempt more 
rigorous testing. Both sanity tests and smoke tests are 
ways to avoid wasting time and effort by quickly 
determining whether an application is too flawed to merit 
any rigorous testing

Smoke Testing:-

1. Area of smoke testing is so big.
2. Smoke testing is not a formal testing.
3. Before the build is released Smoke testing is done by 
developers or by testers before accepting a build for 
further testing. 

Sanity testing:-
1. Particular functionality is tested in Sanity testing.
2. sanity testing is formal testing.
3. At the beginning and ending of each phase of Software 
Development Life Cycle sanity testing is performed.
Usually tester and Developer perform Sanity testing.

Sanity Testing : When we will get that New build Major 
Business Functionalities are focused

Somke Testing : To ensure that application is eligible for 
further testing