Difference between White Box, Block Box and Gray Box Testing

Difference between White Box, Block Box and Gray Box Testing:

White Box Testing

White box testing strategy deals with the internal logic and structure of the code. White box testing is also called as glass, structural, open box or clear box testing. The tests written based on the white box testing strategy incorporate coverage of the code written, branches, paths, statements and internal logic of the code etc.

In order to implement white box testing, the tester has to deal with the code and hence is needed to possess knowledge of coding and logic i.e. internal working of the code. White box test also needs the

tester to look into the code and find out which unit/statement/chunk of the code is malfunctioning

Black Box Testing

Black Box Testing is not a type of testing; it instead is a testing strategy, which does not need any knowledge of internal design or code etc. As the name "black box" suggests, no knowledge of internal logic or code structure is required. The types of testing under this strategy are totally based/focused on the testing for requirements and functionality of the work product/software application. Black box testing is sometimes also called as "Opaque Testing", "Functional/Behavioral Testing" and "Closed Box Testing".

Gray Box Testing

             Gray box testing strategy is a combination of both White and Black box testing strategy. This Strategy is used in small concerns where the testers and the developer are the same. This is best suitable for the concerns that develop their own product. Here, they will use all the methodologies used in Black and White box testing.

White Box Testing

Unit Testing

•       Testing of Individual Unit (E.g. : Function, Program, Module)

1.       Also referred to as White Box Testing

2.       Typically performed by the Developer

3.       Goal of Unit testing is to uncover defects using formal techniques like:

•       Resource-behavior (e.g. memory leaks), performance or robustness testing, as well as structural testing

•       Defects and deviations in Date formats

•       Special requirements in input conditions (for example Text box where only numeric or alphabets should be entered)

•       Selection based on Combo Box’s, List Box’s, Option buttons, Check Box’s

•       Testing occurs with access to the code being tested, with the support of the development environment, such as a unit test framework or debugging tool.

4.       The testing must ensure:

•       Statement Coverage

•       Branch Coverage

•       Condition Coverage

•       Exceptional Conditions Coverage

5.       Tools that can be used:

•       Junit, JTest Case, Cactus, Jindent, Rational Quantifier, Rational Purifier

You may also like:
Complete Testing Material

Testing basic interview questions