A little understanding of black box testing with white box test

White box test: It is tested by the source code of the program without using the user interface. This type of test requires the discovery of the internal code from the code syntax in terms of algorithms, overflows, paths, conditions, and so on shortcomings or errors, and then corrected.

Black-Box testing: Also known as functional testing, data-driven testing, or specification-based testing, is rigorously tested by using the entire software or some kind of software feature, without checking the program's source code or knowing exactly how the software's source code program is designed. Testers understand how the software works by entering their data and then looking at the results of the output. (above from Baidu Encyclopedia)

My understanding is the white box test, is to test the source code, just like we do on the OJ, with some representative data to test the feasibility and comprehensiveness of the entire program, and the black box test, as the name implies, is the whole program as a black box, we do not see this program in the case of testing, We are standing in the user's point of view, to test the operation of the software, to compare the function of the software and the requirements of the written content, compared to the white box test, black box testing should be considered complementary to the white box test test, you can find some in the case only see the program is not found problems and errors.

White box test main test content (currently thought of):

1, the data structure test;

2, the logic true and false test;

3, for the loop nesting and jumping out of the boundary test;

......

The main contents of the Black box test:

1, performance testing;

2. Function test (Control requirement specification);

2, whether there are obvious data structure errors;

3, software security testing;

4, stability test pressure test and so on.

A little understanding of black box testing with white box test