Smoke Testing: In this testing we will check whether all 
componenets are present or not. Where as in Sanity we will 
check all components are working properly or not.

Ashok Kumar Gurram,hi this is not eorrect answer as i 
experience .sanity and smoke differece is there or not .i 
don't know but smoke testing is checking all the major  
functonalies are not checking before relaesd to the testing 
team at inc or system testing level

BOTH THE ABOVE ANSWER ARE RIGHT TO CERTAIN EXTEND.LET ME RE-
PHASE IT, SMOKE TEST WE PERFORM AFTER EACH AND EVERY 
BUILD,VERSION CHANGE ETC. THIS TEST WE TRY TO FIND WHETHER 
ALL THE CONDITIONS IS MET AS WE DERIVED.
NOW SANITY TEST IS THE ONE WHEN WE DO THE INITIAL TESTING 
OF ANY SOFTWARE WHETHER SOFTWARE IS ACCEPTABLE FOR 
TESTING.GENERALLY ITS THE FIRST TEST, WHEN A QA IS CALLED 
FOR AFTER THE APPLICATION IS DEVELOPPED.

Checking the major functionality in an application is called
smoke testing 
Checking the minor functionality in an application is called
sanity testing

as of my knowledge, just before relasing the build the 
developers will check whether the build is proper forhter 
detailed testing or not . that is known as smoke testing 
and once the build is relaised the test engineers will 
check whether the build knos as sanitary testing

smoke testing will check all the functionalities in the 
application,but not go deeply into it(otherwise we can say 
BVT(Build verification test)
sanity testing wiil check major functionalities and deeply 
go into that
both will prepare the application to be testable one

Smoke and Sanity testing both perform the same type of 
checking which is whether the software should go for major 
testing or not. The difference lies, Smoke Testing is 
performed at developers end by the developer and in 
contrast Sanity Testing is performed by the tester.

And i can gurantee this is 100% correct answer.

According to FUNDOO who replied and I write:
"Smoke and Sanity testing both perform the same type of 
checking which is whether the software should go for major 
testing or not. The difference lies, Smoke Testing is 
performed at developers end by the developer and in 
contrast Sanity Testing is performed by the tester.

And i can gurantee this is 100% correct answer.
"
Well, Fundoo it seems you are new to QA 
experience/business. Don't comment that your answer is 100% 
correct answer which is distorted & Confusing to those 
persons who are reading this site.
First of all: The Smoke test are done each and every time, 
if the version is changed, that has nothing to do with 
developers etc. Yes, are you using Automation. If yes, then 
the smoke test are done by the Autoamation team(expert) 
after the developers have given the software to the QA 
team. Well if your company is small then it may be the 
developer doing that, then in that case you are a Tester 
not a QA. Regarding the Sanity Test, that is performed 
first time, when the application is developed. Later you 
have Smoke test and lot of regression test before you are a 
new version is developed. And the cycle goes on and on. I 
hope to the readers that the confussion is cleared after 
reading this.

Here are the differences you can see:


SMOKE TESTING:

1)Smoke testing originated in the hardware testing practice 
of turning on a new piece of hardware for the first time 
and considering it a success if it does not catch fire and 
smoke. 
2)In software industry, smoke testing is a shallow and wide 
approach whereby all areas of the application without 
getting into too deep, is tested. 
3)A smoke test is scripted, either using a written set of 
tests or an automated test 
4)A Smoke test is designed to touch every part of the 
application in a cursory way. It’s shallow and wide. 
5)Smoke testing is conducted to ensure whether the most 
crucial functions of a program are working, but not 
bothering with finer details. (Such as build verification). 
6)Smoke testing is normal health check up to a build of an 
application before taking it to testing in depth. 

SANITY TESTING:

1)A sanity test is a narrow regression test that focuses on 
one or a few areas of functionality. Sanity testing is 
usually narrow and deep. 
2)A sanity test is usually unscripted. 
3)A Sanity test is used to determine a small section of the 
application is still working after a minor change. 
4)Sanity testing is a cursory testing, it is performed 
whenever a cursory testing is sufficient to prove the 
application is functioning according to specifications. 
5)Sanity testing is a subset of regression testing. 
6)Sanity testing is to verify whether requirements are met 
or not, checking all features breadth-first. 
Hope these points will help you to clearly understand the 
Smoke and sanity tests and will help to remove any 
confusion.