Sanity Testing is the processes of 
checking the basic functionality of the application. This 
testing are done before the application is cleared for in 
depth testing. 

There is no point of testing further if the basic 
functionality are not working properly.

Sanity Testing are performed to check whether the
Application is sane enough to proceed  for Major 
Functionality .

Both Smoke & Sanity testing are same in one way that is, 
its a build verification testing. When a particular module 
is developed then developer will do smoke testing in order 
to test whether the developed module is stable (which means 
the basic functionalities must work) then in turn it will 
be given for testing.

Now the testers will also do the build verification testing 
where we call that as Sanity testing

a)	Sanitary testing is nothing but the build is stable 
or not complete to testing is called sanitary testing.  

b)	Sanitary testing is also known as testers 
acceptation testing (TAT), or builds verification testing 
(BVT).

c)	Now check the lock and fell, that telephone have 
the connection or not, if connection have that is which 
type, all numbers are work or not, that size, this type of 
all testing apply the telephone.

Sanity testing is performed whenever cursory testing is 
sufficient to prove the application is functioning 
according to specifications. This level of testing is a 
subset or regression 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

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

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

sanity testing: 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.

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.

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

Sanity testing is testing the application to 
ensure, if it is stable enough to continue further 
testing.If the test fails ,we cannot continue testing 
further.Sanity testing is the initial test after the build 
release.It is done by the QA team.

Sanity testing is subset of regression testing and it is in 
testing the build in depth.
e.g For login screen 

According to me
smoke testing and sanity testing  both are same,but some 
organizations follow the smoke r sanity testing after 
receiving the build from the dev the testers check whether 
the high level functionalities of the app working correctly 
r not.

Sanity testing, This is also called tester
Acceptance testing.

This is to determine, Whether the supplied build is 
testable or not, 
So 
   Sanity Test -Tester Acceptence Test(TAT)
these are the very first tests conducted by the testing 
team.
Also called as level -zero tests in STLC.

Testing...Basic functionalities..(check 
box..list box...buttons...etc.) are working or not...in an 
application.

Sanity testing means initial testing done to check the 
environment well suites for the testing process or not..

Once a new build is obtained with minor revisions, instead 
of doing a through regression, 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 app.

Sanity test cases is the test of major and critical 
functionality test  cases like navigation authentications . 

Sanity testing is a one time job for application .

After the build is creating the build is 
verified whether the created build can be installed on all 
the operating systems successfully.

testing the application for the latent bug

We have to choose the cases which tests the major 
functionalities of an application.

we have to do this sanity testing at each and every Phase 
as an exit criteria which is to be satisfied.

test cases 4 Sanity testing can be prepared only based on 
the positive functional flow of module or build

sanity testing is seeing if the application is fit enough 
for actual testing. eg: testing the web link, browser etc.

Sanity test is used to validate all major functionalities

sanity testing is to verify whether requirements are met 
or not, checking all features breadth-first.

Once a new build is obtained with minor revisions, instead 
of doing a through regression, 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 app.

the main objective of sanity testing is the build is 
sutable for continuing testing (of next level) or not

1.Sanity testing is testing the application to 
ensure, if it is stable enough to continue further 
testing.If the test fails ,we cannot continue testing 
further.Sanity testing is the initial test after the build 
release.It is done by the QA team

2.It is also known as testers acceptation testing (TAT), or 
builds verification testing (BVT).

It is a type of testing to check the major functionality of 
the application and whether it is stable for further testing

Sanity Testing is also called as Level-0 testing 
tecnique ,in this Level-0, we test the major 
functionalities in our build whether this Software can be 
able to check for further functionalities or not.

Example: Login page

typically an initial testing effort to determine if a new 
software version is performing well enough to accept it for 
a major testing effort. For example, if the new software is 
crashing systems every 5 minutes, bogging down systems to a 
crawl, or destroying databases, the software may not be in 
a 'sane' enough condition to warrant further testing in its 
current state. 

To test whether the build is stable or not once the
development team releases the build

Sanity Testing: It is the initial testing done on the new
software version to determine whether it accept all major
testing effort or not .If it crashes for the initial use
then it is not stable for the further use.

Smoke: From the name itself we can define to test the
functionality of the application.