White Box Testing is just like a transparent glass, in which the tester can see both side of the glass clearly.
One type of WhiteBoxTesting is fault injection testing, a technique used to verify fault-tolerant systems. Highly reliable systems will not fail under black-box stimulus. Code written to handle infrequent failure conditions can only be verified by injecting a fault through white-box testing. 

Another use of white-box testing is to test interfaces for robustness. This is good practice when you open up that interface to truly external devices that may not properly implement according to an interface specification. Analysis of the code may indicate possible weaknesses related to violations of the spec, guiding the selection of test data to exercise specific cases that might cause an undesirable failure state. 
----
WhiteBoxTesting implies access to the code of the application and the ability to test every line of code within it.

For more on WhiteBoxTesting (also known as G''''''lassBoxTesting):
*http://www.issco.unige.ch/ewg95/node81.html#SECTION00731000000000000000
*http://www-106.ibm.com/developerworks/rational/library/1147.html
*http://www.webopedia.com/TERM/W/White_Box_Testing.html
*http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/coverage/whitebox.html
*http://www.sdmagazine.com/search/
*http://www.faqs.org/faqs/software-eng/testing-faq/section-13.html

----

One kind of WhiteBoxTesting is "TestCoverage".

----
Contrast BlackBoxTesting
----
CategoryTesting