Some basic things about White-Box Testing and relevant stuff !

Let's start with basic understanding of White Box Testing first -

White box testing is a method to test the functionality of the code by passing parameters within the code itself.
White box testing involves looking at the structure of the code. When we know the internal structure of a product, tests can be conducted to ensure that the internal operations performed according to the specification. And all internal components have been adequately exercised.
White box testing is also called Structural testing or Glass box testing.


How to approach for White Box Test Planning and Execution :-

In general prerequisites for white box testing are the same as for black box testing. The only difference is the access to the application source code. The white box tester should ask for detailed requirement, functional specifications, high-level design documents, detailed design documents and source code. The white box QA Engineer would analyze the source code and prepare test cases for testing the functionality to ensure that the code is behaving according with the requirements and specifications.


Biggest Limitation of White-Box Testing

Test-Coverage. With most of the White Box Testing techniques,  it's hard to achieve reasonable program paths and you always need to plan testing appropriate workflows.

PROS and CONS of White Box Testing and Black Box Testing.

White Box testing:

Advantages
1) more code coverage
2) more error can be found earlier during the development process.
3) The whitebox testing could start in the early phase along with software development.
4) Just a main module from developer is enough to start to test by using stubs.
5) helps giving more stable build

Disadvantage:
1) more time consuming to develop test cases as it involves development effort
2)often new architecture need to be designed to suit your testing needs.
3) Testers need to be involved in requirements , software design document review also.

Black Box Testing:

Advantages:
1) testers need not know the softwrae design of the SUT
2) requirements are enough to develop test cases
3) Black box tetsing is usually done manual except
 

Disadvantages:
1) more time required to test each test case and verification results
2) less code coverage
3) some scenarios can be eliminated due to human error or ignorance of the system.


Cyclomatic complexity is a software metric which measures the number of linearly independent paths through a program source code.

V(G) = E-N+2

where, E=No. of edges, N=No. of nodes