White box testing

I searched some information about white box testing, which helps me understand it better.

White-box testing is a method of testing the application at the level of the source code.

These test cases are derived through the use of the design techniques mentioned above: control flow testing, data flow testing, branch testing, path testing, statement coverage and decision coverage as well as modified condition/decision coverage.

White-box testing is the use of these techniques as guidelines to create an error free environment by examining any fragile code. These White-box testing techniques are the building blocks of white-box testing, whose essence is the careful testing of the application at the source code level to prevent any hidden errors later on. These different techniques exercise every visible path of the source code to minimize errors and create an error-free environment. The whole point of white-box testing is the ability to know which line of the code is being executed and being able to identify what the correct output should be.

Here's the basic procedure of white box testing:

• Input involves different types of requirements, functional specifications, detailed designing of documents, proper source code, security specifications.This is the preparation stage of white-box testing to layout all of the basic information.
• Processing involves performing risk analysis to guide whole testing process, proper test plan, execute test cases and communicate results. This is the phase of building test cases to make sure they thoroughly test the application the given results are recorded accordingly.
• Output involves preparing final report that encompasses all of the above preparations and results.
  

There are many advantages of white box testing.

• Side effects of having the knowledge of the source code is beneficial to thorough testing.
  
• Optimization of code by revealing hidden errors and being able to remove these possible defects.
  
• Gives the programmer introspection because developers carefully describe any new implementation.
  
• Provides traceability of tests from the source, allowing future changes to the software to be easily captured in changes to the tests.
  
• White box tests are easy to automate.
  
• White box testing give clear, engineering-based, rules for when to stop testing.

Some from wikipedia.