The basic concept of black box testing, the white box and gray box testing:. Aken1 black box testing, also known as black box testing functional or drive test data, it is known that the product should have the function to detect each of the tested Whether the function can be used normally, when testing, treating the program as a black basin that cannot be opened, the tester tests in the program interface without considering the internal structure and internal characteristics of the program, it only checks the program function Whether or not the program can properly receive the correct output information in accordance with the requirements of the requirements specification specification, and the program can properly receive the correct output information, and maintain external information (such as database or file) integrity. The black box test method mainly has equivalence classification, boundary value analysis, due to fruit pictures, error speculation, etc., mainly for software confirmation testing. "Black Box" method is the external structure of the program, regardless of the internal logic structure, testing the software interface and software function. The "black box" method is exhausted input test, only use all possible inputs as a test case, in order to find all the errors in the program in this way. In fact, there is a number of infinity tests, but also do not only test all legal inputs, but also test those non-legal but possible inputs.
2. White box test white box test is also known as structural test or logical drive test, it is known that the internal work process can be tested to detect whether the internal action is normal in accordance with the specification of the specification, according to the structure test procedures inside the program, Whether each passage in the inspection process can work correctly according to the scheduled requirements, regardless of its function, the main method of the white box test has logical drive, basis test, etc., mainly for software verification. "White Box" method fully understands the internal logical structure of the program and tests all logical paths. "White Box" method is exhausted path test. When using this scenario, the tester must check the internal structure of the program, from the checkpoint logic, to draw test data. The number of independent paths throughout the program is an astronomical figure. But even if each path is tested, there may still be errors. First, the exhaustive path test must not detect the program violates the design specification, that is, the program itself is a wrong program. Second, the exhaustive path test is impossible to detect the procedure for missing paths. Third, the exhaustive path test may not find some errors related to data.
3. The gray box tests the gray box test. It is indeed between the two, which can be understood that the gray box test pays attention to the correctness of the input, but also pays attention to internal performance, but this is not like a white box. Complete, only through some characteristic phenomena, events, flags to determine the internal operational state, sometimes the output is correct, but the internal is actually wrong, this situation is very much, if each time it passes through white box test Operation, the efficiency will be low, so a method of such a gray box is required. The gray box test combines the elements of the white box test box black box test. It considers the user-end, specific system knowledge and operating environment. It evaluates the design of the application in the collaborative environment of the system components. The gray box test consists of methods and tools, these methods and tools can be used in the environment of the application's internal knowledge box and interaction, which can be used in black box testing to enhance test efficiency, error discovery, and error analysis. Gray-in-box tests involve input and output, but use information design tests that are usually in terms of test staff from code and program operations.
-------------------------------------------------- -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
[Author] Network name: aken work time: 5 years of professional expertise: web application test, automation test, test tool write .mail: aken2004@126.com
