AS their name indicates
Smoke Test means: Build Verification Test(BVT)
                  checking the Build is stable or not.
Sanity Testing: Tester Acceptence Test(TAT)
                Checking the given Build is testable or not
                That means checking all features are  
                working and accesssible or not.
But one thing In most of the testing companies  even in Some
Big MNCS  the above two are considered as same.

to be continues...........

rajendra_penumalli@yahoo.com
9885162742
hyd

After getting the build, first we will be doing sanity 
testing to conform whether the given application is able to 
carry for further testing.

Smoke testing is that after completing the whole testing of 
the build, we will be checking the build is stable or not.

a)	In smoke and sanity 1st conducting the sanity 
testing.
b)	Sanity testing is nothing but whether the 
development team release build is a, is table for complete 
testing or not test is called the sanity testing.
c)	That is the build start to end is possible, no 
middle brakes, if some navigation after the build and with 
system hang or not this types of tests
d)	This sanity testing also is called the Tester 
acceptation testing (TAT) or build verification test (BVT) 
e)	This test is monitory test also
f)	Now smoke testing is nothing but it is a small 
change a in a sanity testing process.
g)	That is in above (in sanity testing) what test are 
conducting now the tester if any problem arise then in 
tests, then reject build with reasons, build is not working 
it is called the smoke testing.
h)	Smoke testing is also known as the optional testing 
also.
i)	Actual it the both process but now the MNC 
companies are follow the when the problem arise, (remember 
it not test execution it is only 1st build verification 
test only) then stop the test on the build the intimate the 
developments team.
j)	So all are doing smoke testing only that here 
verify and intimate also.


My name is k.chandra sekhar
My phone no is 09246540049
I am in hyderabad
My mail id is ndra_143@yahoo.co.in 
If any body want full explain send that mail

Smoke Testing: in which one can perform initial an short 
span testing conducted on the application to check if all 
the required windows/features/objects are basically 
available in order to carry on the detailed testing on 
it.So the smoke testing is referred as availability testing.

Sanity Testing: it is also same as Smoke testing, but it 
checks for proper availability.

Hey please dnt give wrong answers ...

whenever a build is released first of all we do smoke 
testing to check whether the build is ready to take further 
testing.its just to check the major funtionality ..

Sanity testing is in depth testing which cover all the 
major and minor functionality of a project..

for e.g let to check module A , B , C is called smoke 
testing than in depth testing of these modules like in <A> 
a1,a2,a3.. than in function <B> b1,b2,b3 ,i mean in depth 
testing of major functionality,is called sanity testing..

in sanity we dnt need to execute test cases..

smoke testing - build verification test
which is done by release engg team near develovpement 
enviroment
sanity testing- done by qc testers near deployment 
enviroment

There is not much difference between smoke and sanity testing.

The functionality testing we do for both is the same. The
type of testing we do is same but the only difference is the
team who does it.

Smoke testing: it is also called as Build Verification Test.
The developer's team after finishing there coding part they
go through the entire application which they complete (
which we call is a build) to check whether it is working
properly according to there requirement. Here each and every
developers check there own functionality and once they feel
it is good then they give a statement to tester team that
build is ready to test.


Sanity Testing:-  It is also called as Tester verification
Test.Now to accept the build which developers are given
tester too check for the minimal functionality working
conditions. They check the minimal functioanlity and check
whether it is suitable for the testing team to conduct
testing or not.

         In one way tester check whether the build is in
testable condition or not.


THe way the functionalit testing goes is exactly the same in
both smoke and sanity testing. the only different is
developers conduct they test called as smoke testing before
they hand over the build to testers  and testers check the
functionality of the build to check whether it is suitable
to accept for further major testing before accepting the
build of testing.


I hope this might help you.