White box testing:

• White box testing is performed at system or module level by a team to know the most important paths of source code.
• It is performed after unit testing is done by developers.
• This testing is done either on the host or target.
• It checks the code coverage.
• It checks software from code point of view. It will not check whether the requirements are met and complete in the first place.
• The focus of White Box testing is to only check the way the code written is proper.
• White box testing will not check for missing codes or faults.
• Change in code because of change in requirements, design or fixing of a major bug all such tests that depend on the changed code get affected.
• This testing is not performed with isolation from development team.

• White box testing is also inadequate in testing for system issues such as system timing requirements, hardware interfaces, load, stress testing.

  

Black Box Testing:

• It is also called as functional testing which looks at the system from a requirement’s point of view.
• It checks to see if system is able to satisfy all requirements expected out of it.
• There is no focus on code coverage.
• It is independent of the way the system has been designed and implemented.
• Black box testing and development teams perform their jobs independent of each other.
• Functional testing looks at the system from requirement point of view, it is best suited for testing non-functional requirements.
• It also finds problems that are not detectable by regression testing or code based testing.
• If the specification for the software good, are the specification changes rapidly, black box testing nice to keep pace with it limiting its effectiveness.

• It will not perform the analysis of code coverage.