White Box Testing:

1. White Box testing is performed at system or module level by a team to know the most important paths of source code.
2. It is performed after Unit testing is done by the compilers.
3. This testing is done either on the host or target.
4. It checks the code coverage.
5. It checks the software from code point of view. It will not check whether the requirements are met and complete in the first place.
6. The focus of White box testing is to only check the way the code written is proper.
7. White box testing will not check for missing codes or faults.
8. 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.
9. This testing is not performed with isolation from development team.
10. White box testing is also inadequate for testing system issues such as system timimg requirements, hardware interfaces, load, stress testing.

Black Box Testing:

1. It is also called as functional testing which looks at a system from a requirements point of view.
2. It checks to see if the system is able to satisfy all requirements expected out of it.
3. There is no focus on code coverage.
4. It is independent of the way the system is designed and implemented.
5. Black Box Testing and development teams perform their jobs independent of each other.
6. Functional testing looks at a system from requirements point of view, it is best suited for testing non functional requirements.
7. It also finds problems that are not detectable by regression testing or code-based testing.
8. If the specification for the software is not good, or the specification changes rapidly, black box testing needs to keep pace with it, limiting its effectiveness.
9. It will not perform the analysis of code coverage.