How to guarantee the coverage of black box testing (RPM)

1, first Test demand analysis to comprehensive

The test requirements analysis is divided into two steps:

1. Acquisition of test requirements

Sources of demand:

Explicit requirements:

(1) Original requirement specification

(2) Product specification sheet

(3) Software requirements documentation

(4) Documents with or without inheritance

(5) Experience Library

(6) General Protocol specification

Implicit demand: The user's subjective feelings, the mainstream view of the market, the evaluation of professionals

2, analysis of requirements, production of test requirements documentation

The different sources of demand are divided into demand points for testing and analysis for each point:

(1) Define the scope of the test

(2) Test points are generated using a variety of test design methods

In terms of testing methods, the following notes can be made:

First, analysis of export access. From the analysis of the entrance, the possible environment, conditions, operations and other content classification combinations, and then according to the test method for the integration of the people, each verification. From the export analysis, the possible results are counted, according to the results of the different origins, and then find different operations and conditions and other content, statistics into documents, each verification.

Second, a variety of test methods of learning and use. People may be more concerned about the test method, but the specific operation of the technique also needs to be noted. After all, the test method is easier to find, you are very familiar with people. If you summarize each person's different testing techniques and use them in your own test implementation, you may receive unexpected results.

In the testing process, the following notes can be made:

First, need to do a good job in the early analysis. Gradually refine the requirements to small function points and test the design for each function point. For the completed test design documents, after the project related personnel inspection review, to make the required first draft.

Second, in the test process, according to requirements change and specific test execution process encountered problems to improve the test design documents.

Third, after the test execution, to summarize the problems that arise. It contains the problems that are found in itself, as well as questions that customers may ask. The results are integrated into the test design to further improve the test design documentation.

For a single test, it is impossible to have a comprehensive coverage test. Need to sum up a lot of accumulation, will make the test more and more comprehensive.

In the field of test flow thinking, the following notes can be made:

First, testing is not equal to comprehensive testing. Different stages have different requirements for software testing, for example, before the 0.8 release, there is no need to care about unimportant picture problems or small functional problems. But in the acceptance phase, these things may be more important to note.

Second, learning, only constantly to learn constantly to think, to make their own ability to test more powerful, test subjects of comprehensiveness is more complete.

2, when the test requirements analysis is completed, and the formation of documents, to conduct testing requirements review, to ensure the accuracy and completeness of requirements.

3. After the test requirements are completed, test cases can be designed according to the test requirements.

To ensure that the test case can fully cover the test requirements, include all the circumstances.

Test case design is divided into single-function test cases and test scenario design , single-function testing covers the requirements of the functional points, test scenarios to cover the requirements of business logic.

When designing test cases, you can use a variety of test case design methods.

First, the equivalence class division, including the input condition and the output condition equivalence class division, reasonable set effective equivalence class and invalid equivalence class, which is the most effective method to reduce workload and improve test efficiency.

L must use the boundary value analysis, and experience shows that the use case can find many bugs in this method.

L can use the error-guessing method to append some test cases, which depends on your wisdom and experience.

L Check the logical coverage of the designed test cases against the program logic and should be supplemented with sufficient test cases if the coverage criteria are not met.

If the function description of the program contains the combination of the input conditions, the causal diagram and the decision table-driven method can be selected from the outset.

For the software of parameter configuration class, the orthogonal test method is used to select less combination method to achieve the best result.

For a system with clear business flow, the scenario method can be used throughout the entire test plan process to comprehensively use various test methods in the case.

When the test case design is completed, to organize the review of test cases, so that you can draw other people's opinions, reduce omissions, complete test trial examples.

4, after the test case is written, is the test execution,

L test Case Execution 100% overlay.

• Continue to complement test cases during test execution to ensure that test coverage is increased.

5, throughout the testing process, the requirements are not immutable, so to update the test requirements, test cases in a timely manner.

6. Correlate test requirements, test cases, and bugs found for easy management and tracking, while also making it easy to see coverage.

How to guarantee the coverage of black box testing (RPM)