Sanity testing is an initial testing where the tester will
check major functionality is working or not.

Smoke testing is similar to sanity testing but here checking
the major functionality b/w two modules

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 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

A unit of code contains a set of reciprocal functions, 
usually in the form of conversion functions where one 
converts A to B and the other converts B to A. In these 
cases, it is useful to create a “sanity check” to make sure 
that you can convert A to B and back to A without losing 
precision, incurring rounding errors, or triggering any 
other sort of bug.