Personally think that the black box test is easier than the white box test, professional things are not obvious, even if the software developers can also be black box testing software, black box testing is mainly for software functions and compatibility testing, no need to see the code, just to verify whether the software to complete the requirements of the function, Here are the specific steps and methods for conducting a black-box test: Black-box test steps
(1) Test Planning phase
First, according to the user needs report on the functional requirements and performance indicators of the specification, define the corresponding test requirements report, that is, the highest standards of black box testing, all future testing will be around the test requirements to be carried out, in line with the test requirements of the application is qualified, the reverse is not qualified; Also should choose the test content appropriately, the reasonable arrangement test personnel, the test time and the test resources and so on.
(2) Test design phase
According to the program requirements specification or user manual, according to a certain standardized method of software function division and design test cases.
(3) test development
Establish a reusable automated testing process.
(4) Test Execution phase
Perform the automated test process established during the test development phase and follow up the identified defects. Test execution is generally composed of unit test, combination test, integration test, System interlock and regression test and so on, the test personnel should be in a scientific and responsible manner, step by step test.
(5) Test Summary phase
Combined with the quantitative test coverage and defect tracking report, the quality of the application software and the development team's work progress and efficiency are comprehensively evaluated.
Black box test the error type of the main test
① incorrect or omitted functions;
② interface, interface error;
③ performance error;
④ data structure or external access error;
⑤ initialization or termination condition errors, and so on.
Methods of black Box testing
Black-Box testing has two basic methods: passing Tests and failing tests.
When you pass the test, you are actually confirming what the software can do without testing its capabilities. Software testers use only the simplest and most intuitive test cases.
When you design and execute a test case, you always pass the test first. Before destructive testing, take a look at whether the basic functionality of the software can be achieved. This is important, otherwise you will be surprised to see why so many software defects appear in the normal use of the software.
After making sure that the software is running correctly, you can take a variety of tools to find flaws by doing "break" software. Test cases that are designed and executed purely for the purpose of destroying the software are known as failure tests or forcing error tests.
Talking about black box test