Sanity testing is performed whenrver cursory testing is 
sufficient to prove the application is functioning 
according to specifications.This level of testing is a 
subset or regeression testing.

smoke testing: Smoke testing is done by developers before 
the build is released or by testers before accepting a 
build for further testing.
sanity testing: sanity testing is done whether we can go 
advanced testing or not for example 
open browser and type the exact url of application in the 
application bar if corresponding page has been opened then 
we can go for further  testing if not rejects

Sanity Testing:

     This testing will be done by the tester to check 
whether the new application is ready for the major testing 
effort.

Smoke testing :

   this just like sanity testing, but this testing will be 
done by the developer before releasing to the tester for 
the further testing.

SmokeTesting:

Verifying whether the build is ready for testing or not.
If the smoketesting fails we don't need log any bug.
We can directly reject the build.

SanityTesting:

In this testing all the major & critical functionalities of 
an application.

sanity testing:the build is stabule or not
smoke testing:all screens or opening or not,all buton

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.


y name is k.chandra sekhar,
My phone no are 9246540049 65880049 ,Hyderabad.
My mail id is ndra_143@yahoo.co.in 
I am take the class for projects if you interst contact
If any body want full explain send the mail

sanity testing :  in sanity we will check the 
functionalities like briefly for example in gmail whether 
the inbox window is displaying r not and compose mail 
window and drafts window like that....

smoke testing : In smoke we will test the major 
functionalities like whether the appropriate edit box is 
able to take characters r not and in some projects some 
values will be reflect to the another window at that it is 
able to reflect r not that we will check in smoke.

Sanity testing:
Sanity testing nothing but the tester goes to developer 
place and perform some test without write any testcase.

Smoke testing:
smoke testing is noting but testing the major 
functionalities.That means once the tester receive the 
build, first he/she need to test the major functioalities 
of the module the major functionalities not satisfied the 
smoke test we just reject the build.

Sanity Testing is the Initiative testing we are conducting
for STLC cycle where as Smoke testing is conducting
by the developers before releasing the software build to the
testing phase.

Sanity testing is conducted by the Testers where as smoke
testing is conducted by the developers.

Based on the Sanity testing results testers will identify
the received initial build is further testable or not
And based on the Smoke testing developers will identify the
all the functionalities have been covered or not ...

regards
Sm