"Software Test" grey box testing

Gray box testing, is between the white box test and black box test, it can be understood that the gray box test is concerned about the correctness of output for input, but also pay attention to internal performance, but this concern is not as detailed and complete as the white box, but through a number of representational phenomena, events, signs to determine the internal operating state, sometimes the output is correct , but the internal is actually wrong, this situation is very much, if every time through the white box test to operate, the efficiency will be very low, so need to take such a gray box method.

Characteristics of gray Box testing:

The grey box test combines the features of the black box test with the White box test box. It considers the client side, the specific system knowledge and the operating environment. It evaluates the design of the application software in the collaborative environment of the system components.

Gray box testing consists of methods and tools that are based on the environment in which the application's internal knowledge box interacts with it, and can be used for black-box testing to enhance efficiency in testing, error detection, and error analysis.  

Gray-Box testing involves input and output, but it is designed to be tested with information about code and program operations, which are typically outside the visual field of the tester.

Black hundred box test and the relationship between:

1, black box test may be a dynamic test (run the program, only look at the input and output), there may be static testing (do not run the program, just look at the interface)
2, white box test may be dynamic test (run the program, and analyze the code structure), it may also be static testing (do not run the program, just static View code)
3, the dynamic test may be a black box test (run the program, only look at the input and output), there may be a white box test (run the program, and analyze the code structure)
4, static testing may be black box test (do not run the program, just look at the interface), it may also be a white box test (do not run the program, just static View code)

What are the benefits of performing a gray box test?

1 . Be able to perform requirement-based coverage testing and test based on program path coverage;

2, the test results can correspond to the internal path of the program, easy to locate, analyze and solve the bug ;

3, to ensure the integrity of the design of the black box test cases, to prevent the omission of some of the software is not commonly used function or function combination;

4, the ability to demand or design is not detailed or incomplete on the impact of testing.

So what are the drawbacks of a grey box test?

1, the time to invest more than black box test about 20-40% of the time;

2, the test personnel of the technical requirements are higher;

"Software Test" grey box testing