The difference between black box testing, white box testing, and gray box testing

1. Black box testing.

A black box, as the name suggests, is to put everything in one box, and you can't see the internal logic, but only through the external visible functional modules, and test the software.

For example, if you don't know what the internal logic of a ** login function is, you can only test whether the registration function is normal through the registration input text box and registration button on the web page. General black box testing is also called data-driven testing or functional testing (by entering data to determine whether the function is complete or normal), and it generally focuses on the following points:

1. Are there any incorrect or missing features?

2. On the interface, can the input be accepted correctly? Can you get the right results?

3. Is there a data structure error or an error in accessing external information (such as data files)?

4. Can the performance meet the requirements?

5. Are there any initialization or termination errors?

2. White box testing: White box testing is a detailed examination of the process details of the software. This approach treats the test object as an open box, which allows the tester to design or select test cases and test all the logical paths of the program using the logical structure and relevant information inside the program. Determine if the actual state is consistent with the expected state by checking the program status at different points.

For this reason, white-box testing is also known as structural testing or logic-driven testing. (General interface testing can also be understood as white-box testing, you clearly know the logical direction of each business flow, and you can effectively formulate some test cases, without blindly doing various tests through function points).

The white-box test is mainly to check the program module as follows:

1. Test all independent execution paths of the program module at least once.

2. For all logical judgments, take "true.""Both cases and "fake" can be tested at least once.

3. Execute the loop within the boundaries of the cycle and the boundaries of operation.

4. Test the validity of internal data structures, etc.

Grey box testing. Gray box test is between the white box test and the black box test, it can be understood in this way, the gray box test focuses on the correctness of the output for the input, but also pays attention to the internal performance, but this attention is not as detailed and complete as the white box, just through some representative phenomena, events, signs to judge the internal operating state, sometimes the output is correct, but the internal has actually been wrong, this situation is very many, if every time through the white box test to operate, the efficiency will be very low, Therefore, such a gray-box approach is needed.

However, in fact, there are very few areas used in gray box testing, so I will not go into detail here.

Black-box testing: Penetration testers only know which system is being tested, but they don't know any information inside the system. Penetration testers are like standing in a dark room, they can't see anything, and they can only get out if they find vulnerabilities.

I don't know at all, I can only explore little by little.

White-box testing: penetration testers know the details of the target system in advance, and in this case, penetration testers mostly screen out possible problem points one by one based on experience or standard operating procedures.

Gray box test: white + black is gray, gray box test is a method between the above two tests, there is a certain understanding of the target system, but also has a certain information, but it is not comprehensive. Penetration testers have to continuously gather information and combine it with known information to identify vulnerabilities.

First, the test method is different.

1. Black box test: Functional test is to test whether each function can be used normally.

2. White-box test: called structural test, transparent box test, logic-driven test or test-based.

Second, the purpose of the test is different.

1. Black box test: Treat the program as a black box that cannot be opened, and test the program interface without considering the internal structure and internal characteristics of the program, and only check whether the program function is used normally in accordance with the provisions of the requirements specification, and whether the program can properly receive the input data and produce the correct output information.

2. White box test: By checking the internal logical structure of the software, the logical path in the software is covered and tested. Set up checkpoints in different parts of the program to check the status of the program to determine whether the actual operating cavity state is consistent with the expected state.

Third, the test principle is different.

1. Black box slow and smooth test: the test is carried out based on the user's angular disturbance wax degree and the correspondence between the input data and the output data. Obviously, if the external characteristics themselves are designed to be faulty or the specifications are incorrectly specified, they cannot be detected by the black box testing method.

2. White-box testing: All independent paths in a module are tested at least once. All logical values need to be tested for both true and false.

The biggest difference between the two is testing.

The object is different, the white box test is mainly aimed at the program** Luo Zhen Zheng Ji, the black box test is mainly aimed at the functions shown to the user by the program, simply put, the former tests the background program and the latter tests the front-end display function.

Black-box testing: The functional design specifications of the product are known, and the test can be carried out to prove whether each implemented function meets the requirements. White Box Testing:

The internal working process of the product is known, and each internal operation can be proved by testing whether it meets the design specifications, and whether all internal components are inspected; The white-box test is mainly to check the program module: test all the independent execution paths of the program module at least once. For all logical judgments, the two cases of taking the "true" feast and taking the "false" can be tested at least once; Execution of the loop body within the boundaries of the loop and the boundaries of operation; Test the effectiveness of internal data structures, and more.

The institution has a unique 1v1 superintendent tracking learning mode, communication at any time if you have questions, enterprise-level projects, courses interspersed with real project explanations of large factories, professional learning plans for benchmarking enterprise talent standards, including mainstream hot technologies, theoretical knowledge + learning thinking + practical operation to create a complete learning closed loop, and experienced practical lecturers.

In terms of test purpose: the purpose of black box testing is to detect whether there are incorrect or missing functions; In terms of data or parameters, whether the input can be received correctly; whether there is a data structure error or an error in accessing external information; whether the performance can meet the requirements; Whether there are initialization or termination errors. The purpose of white-box testing is to determine whether the actual state is consistent with the expected state by checking the state of the program at different points, without compromising its functionality.

In terms of detection methods: the white box test is an exhaustive path test, and the black box test is an exhaustive input test, these two methods are based on completely different points of view, reflecting the two extremes of things, they have their own focus and advantages, imitation but not the most important fingers to replace each other. In modern testing concepts, these two test methods are not distinctly separated, but rather used intersectingly.

By definition, white-box testing needs to find internal defects or errors in algorithms, overflows, paths, conditions, etc., and then correct them. Black-box testing, on the other hand, focuses on testing software functionality and does not involve the internal structure and content characteristics of the program.

Black-box testing is not a substitute for white-box testing, it is complementary to white-box testing, and it is likely to find other types of errors that are not easy to find with white-box testing.

Hello is happy to answer your questions, black box testing and white box testing are two different testing methods in software testing, and their main difference is whether the tester needs to know the internal implementation details of the system under test. Black slag box testing is a functional testing method in which the tester focuses only on the inputs and outputs of the system under test, without the need to know the details of its internal implementation. The tester enters a variety of legal and illegal data to verify that the system responds correctly and meets the functional requirements of the requirements specification.

In contrast, the white-box test requires the tester to understand the internal structure and implementation details of the system under test in order to more deeply check whether the logic and implementation of the system meet the design requirements. White-box testing typically performs detailed scanning and analysis of various program paths, variables, functions, classes, etc., of the system, with the aim of discovering potential logical errors, security vulnerabilities, and performance bottlenecks. In general, black-box testing focuses on whether the system functions correctly, while white-box testing focuses on the internal implementation details and quality of the system.

In real-world testing, the two methods are often used in combination.