Somke testing :- this testing will done by tester , this is 
scripted & Smoke testing will check the all functionality 
of the appliaction but not checking in wide or depth

Sanity Testing :- This Testing will done by Developer , 
this is not scripted & Sanity Testing will check specific 
module of the software and this testing will check in wide 
or depth

sanity
A process of testing whether the CODE is ready for further
testing or Not 

Smoke
A process of testing whether the BUILD  is ready for further
testing or not

both are same,there is no difference in between them

smoke testing: after receiving the build from development 
team to check the stability of the build for further 
testing.

sanity testing :to conduct testing on build after long 
period even though we know that it is working abosultely 
checking once again that application is working or not.

Smoke testing and Sanity testing are one in the same. Though
the titles given to these tests are different, vary from
organisation to organisation and may suggest that these are
separate test types, the purpose of the test is the same.
Sanity/Smoke testing is a subset of tests used to quickly
scan through software to identify high level defects and
quickly evaluate the level of build quality. The most common
use of this type of test is post-build(code, configuration
and environment) to evaluate build quality and environment
stability prior to the initiation of formal functional or
integration test cycles. The implementation of the test can
be both manual or automated.

Even though both means the same but with different names is
whether it is product based or service based one...