[Tool] software test case review

Software Test case review software test

It is very important to review test cases. After the test cases are designed, they should be reviewed and reviewed in an informal and formal manner. During the test case review and review, the following items are checked:

Whether the overall idea of the test case design is clear, whether the system structure and logic are clear, so that the structure or level of the test case is clear, and whether the test priority or sequence is reasonable;

The effectiveness of the test case design and the emphasis of the test are highlighted, that is, whether to grasp the weak links of the modified area, program or system;

Does the coverage of test cases take into account some special scenarios (scenario) in product use and some boundaries and interfaces;

Test case description, whether the prerequisites exist, whether the steps are clear, and whether the expected results (Criteria) meet the product specification or customer requirements;

Whether the Test environment is accurate, and whether the test cases correctly define the conditions or environment required for the test;

The reusability and maintainability of test cases. Good test cases can be reused to ensure the stability of the test;

Whether the test case meets other requirements, such as manageability and easy conversion of automated testing.

After the test case is reviewed, the test case will be modified based on the review comments, and the review will continue until it passes the review. In future tests, if some defects are found and there are no test cases, add new test cases or modify the corresponding test cases in a timely manner. Test cases related to software defects are more effective, and their execution priority is also high. The ratio of defects found in test cases to all software defects is one of the methods to measure the quality and effectiveness of test cases.

[Tool] software test case review