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.


My name is k.chandra sekhar,
My phone no are 9246540049 65880049, Hyderabad.
My mail id is ndra_143@yahoo.co.in 
I am taking the class for projects and interview trips if 
you interest contact

Sanity testing is done whenever the new build release. we 
have to test for the major functionality of the application 
which could stop our testing part continuation.

If it fails, then we  should not continue with our testing 
part. For the eg of telephone, If we check the 
functionality like while lifting the receiver, it should 
give the dial tone. if it fails, then its waste of time to 
continue with the testing phase.

Also called as smoke testing.

sanity testing is a test  which tests the build came from 
the developers is stable or not for testing that is it 
fufils all the requirements of the customer or not.
 also developers develops all the functionalities or not.
 coming to telephone  its phone working or not.
its phone has std r not
its phone havingn isd or n ot
its working properly or not
keypad of the phone is perfectly pressing r not

sanity testing is a 0 level tesing or intial testing or 
smoke testing. It is done to test that whether the build is 
stable for further testing or not.
for sanity testing of telephone
1. check that phone has dial tone or not.
1. check all the key of phone is pressing.

whenever the tester founds the bug, he will inform to the 
developers about the bug and to fix it. the developer than 
fixes the bug and sends to the tester, this process of 
fixing the bug and sending the new version to the tester is 
called Build. 
the tester has to test whether the major functionality of 
the application is working good or stopping us from testing 
is called as sanity testing.

example of telephone is common and u may refer from above 
examples.

         thank you.

A subset of all defined/planned test cases that cover the 
main functionality of a component or system, to 
ascertaining that the most crucial functions of a program 
work,but not bothering with finer details. A daily build 
and smoke test is among industry best
practices

Sanity Testing: 
1. Shallow and wide testing.
2. No indepth functionality testing.

Sanity means that, normal testing to verify that whether 
the build is fit for further testing or not?
Eg.1.
From GUI perspective, we need to test whether all links are 
working fine or not (any broken links?), i.e. if I click on 
one link, whether the page is taking me to that particular 
page or not?

Eg.2. 
In GUI, we need to test that, whether the help is 
documented properly or not? i.e. if the user is stuck any 
point of time, and if help is clicked, whether the page is 
navigating to the exact help context or not?

Eg.3.
As per installation is concerned, we need to verify, 
whether the build is properly getting installed or not? 
Whether the build is compatible (supports for upgradation 
and degradation of other versions) or not?

Eg.4.
If CLI Menus are theer, we need to make sure that, no main 
menus and the child menus are missing.

In a word, we can say that, Usability (GUI), Compatibility, 
Installation, CLI will all comes in to picture for the 
sanity to be done.

---
Thanks,