Gray box testing

Grey box testing is testing that should combine the advantages of black-box and white-box testing each other in the context of test-driven development (also see Extreme Programming ).

The Grey box testing, together with the white-box test that he is also written by the same developers as the system under test. With the black-box test he shares initially unaware about the internals of the system to be tested, because the gray box test is written before the system under test (Test -First Programming ). Thus, sub-components and complete systems can be tested with the low organizational effort of the white-box tests without any test " errors around". Grey box testing as part of agile processes require high discipline or other process methodologies of software engineering such as pair programming or acceptance tests to be practical and successful use. Otherwise, Grey box testing could prove fatal. Grey box testing should not be thoughtlessly seen as a complete replacement for black-box testing.

Without the supporting pillars of agile processes should not be allowed to dispense with the usual Black- box testing the use of Grey- box testing. Grey box testing should be considered as qualitative improvement of white- box testing.

• Test (software)