A discussion of some misunderstandings about the idea of black box testing

I have written some basic things about white-box testing, black-box testing, regression testing, and automated testing. In this issue, I will focus on the difference between white-box testing and black-box testing.

General There is a certain understanding of the concept of box testing, but it is a misunderstanding to think that the tests done by coding are white-box testing, and black-box testing does not require coding.

Although whether it is app testing or software testing, etc., testing can be done using one of the following two methods.

Black box testing is a test to see if each function works correctly. In the test site, the program is regarded as a black box that cannot be opened. The program interface is tested without considering the internal structure and internal characteristics of the program. It only checks whether the program function is used normally according to the requirements of the specification. Whether the program can properly receive input data and produce correct output information. Black box testing focuses on the external structure of the program, regardless of the internal logical structure, and mainly tests for functions.

In theory, black-box testing can detect all errors in the program only by using exhaustive input testing and considering all possible inputs as test cases. There are practically an infinite number of test cases, and one has to test not only all valid inputs, but also those that are not valid but possible. From this point of view, complete testing is impossible. Therefore, by formulating test cases to guide the implementation of testing, ensure that software testing is organized, step-by-step, and planned. Black-box testing behavior must be able to be quantified in order to truly ensure software quality, and test cases are one of the methods to specifically quantify testing behavior.

Advantages of black box testing

1. Basically, no one needs to control it. If the program stops running, it is usually the crash of the tested program.

2. After designing the test case, the work is cool. Of course, it is more difficult to determine the cause of the

crash Disadvantages of box testing

1. The result depends on the design of the test case. The design of the test case is partly derived from experience. The things of OUSPG are worth learning from

2. There is no concept of state transition. At present, some successful examples are basically done for PDUs, and the state transition of the program under test cannot be done.

3. For tests without the concept of state, find and determine The test case that causes the program to crash is a troublesome thing, and the surrounding possible test cases must be confirmed individually.

As for the white box test, it has been said before that it is based on the internal structure test program of the program. Through the test, it is tested whether the internal action of the product is carried out normally according to the provisions of the design specification, and whether each path in the test program can be correct according to the predetermined requirements. Work. For other information about the specific method, I have written it in the previous articles, you can go and see

TestBird - Mobile Game and App Automated Testing Platform