Both are validating 4 whether basic functionality of build 
is stable or not for further testing

Smoke testing is to find out the 'Testability' of the build 
by ensuring the crucial functionalities of the application 
have been delivered. This will done once build released to 
QA. 
Sanity testing: It is cursory testing, can be done any time 
to ensure that application is working properly. mainly 
focus on GUI checking, database connectivity, printer 
connectivity
So both are have their own nature.

Sanity Test:Every time when a new build comes to the 
testing team then firstly sanity testing is done.Sanity 
consists of testing the basic functionalities of the 
application.Now if any major issue is reported then the 
build is rejected and sanity fails.

Now in the next build the testing is done on the reported 
issue and other features are smoked out.This is smoke 
testing.

Sanity : first conduct the sanity testing,then only go to 
further testing,its means to check the basic 
functionalities...

Smoke: its final testing,the particular build is going to 
realease,if its capable of live environment....
                                         kayessor Blr

Smoke testing is done whenver a new build comes to TCOE 
team.if the smoke test pass then only teasting team proceds 
for further testing i.e. basic testing done by the testing 
team.

Sanity Testing:the world sanity means FRIEND whenever the 
developer develops any code he do the testing by 
himself.but he is not sure for what he coded so he colegie 
i.e. friend developer do the testing of that code is called 
sanity. actully sanity testing done by the development team.

Hi,

Smoke Testing:- When a build is received, a smoke test is
run to ascertain if the build is stable and it can be
considered for further testing. Smoke testing can be done
for testing the stability of any interim build. Smoke
testing can be executed for platform qualification tests.
Smoke testing can be done for testing the stability of any
interim build. Smoke testing is done by developers before
the build is released or by testers before accepting a build
for further testing.  
 
Sanity testing:- Once a new build is obtained with minor
revisions, instead of doing a through regression, a sanity
is performed so as to ascertain the build has indeed
rectified the issues and no further issue has been
introduced by the fixes.  Its generally a subset of
regression testing and a group of test cases are executed
that are related with the changes made to the application.

Plz correct me if i m wrong..
Regards..
nitin9360@gmail.com

Thousand mind, mounth and million different thoughts....