Sanity testing is the testing where we test only the major 
functionalities of the project when it comes to testing 
phase 

 where as the smoke testing is testing the build before it 
is given to the testing team and this is also known as 
build verification and this is done by the developer

See sanity testing Example.

Open the Ellamey.com page. See the Functional Requirements
are present on the page r not according to the client
requirement.check all the module pages.This type of checking
called sanity testing.

Now Check the Functionalities of every modules.Example if u
have Google search button , type any matter and click the
button.now the button(Search) is working r not.This type of
checking called smoke testing.

If search button is displaying in the page then it is sanity
testing. then check the functionality is working then it is
smoke testing.

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.

Smoke Testing: It is a negative testing input invalid data 
to test that the application working under invalid 
conditions or not.
Sanity testing: It is purely different to smoke, testing 
the application wether working correctly to specifications 
only.

SANITY TESTING: test the behaviour of the build. Set of 
core tests of functionality to demonstrate to connectivity 
to the database, application servers, printers. It’s 
suitable for window application.

SMOKE TESTING: the base functionality tests preferably 
without any user input steps involved can be installation, 
navigation through the application, invoking or accessing 
all major features. It’s suitable for web applications.

Snity testing: It is the testing to check whether the 
software is ready for system testing. In this we run the 
s/w to check the basic functionality of the s/w


Smoke testing:- Smoke testing is done just for the first 
time after integration testing and before the system 
testing to check that is there any impact on other 
component of the system because of the s/w