Test Case Quality Evaluation

TestUse CasesThe following three factors can be considered for quality evaluation:

 

First, evaluate the quality of a test case, including:

1) traceability of the requirement items in the test case and Requirement Specification Description. For example, we require at least one test case for each requirement entry. The purpose is to evaluate the test requirement coverage rate and analyze the changes to the test requirements.WorkDegree of impact;

2) whether the test case has clear expected results. Generally, the expected results should be clearly described in each execution step of the test case to ensure that the tester can compare with the actual test results and analyze whether the defect report is required, or modify the test case.

3) whether the test case template defined by the company is met. For example, each company may define a test case template. For example, if a "test type" is defined, each test case must be associated with the test type, test cases for each function must cover all test types, such as portability, interoperability, and stability.

Second, evaluate the quality based on the test case coverage rate, including:

1) requirement coverage. For example, we are mainly responsibleSystem TestTherefore, the requirement coverage rate of test cases must reach 100%.

2) coverage of quality characteristics. For example, we adopt the concept of test type in the test case template, and each functional test case must cover all test types by 100%. For the definition of the test type, refer to the ISO 9126 quality model, previous Defect Analysis, and requirement analysis.

3) Test Platform coverage rate. For example, for our current communication products, each function needs to run on different platforms, such as different network element types, interface types, and business types. The coverage of test cases on these platforms is also required to reach 100%.

Third, evaluate the quality based on the effectiveness of test cases, including:

1) defect discovery rate of test cases. The calculation method we use is "number of defects detected in system test divided by the number of executed test cases, and the percentage is obtained ".

2) The defect discovery rate of the scripted test. The calculation method we use is "number of defects found according to the test case steps/total number of defects found, the percentage obtained ". If this percentage is low, it indicates that the design test case is less effective, and the proportion of defects found through exploratory testing is higher.

3) The defect rate missing from the user site is calculated as "number of defects reported by the user site within 6 months, the percentage obtained after dividing by the number of defects detected at the system test level and the number of defects reported by the user on site within 6 months ".

Each company and test team have different metrics for evaluating test case quality. The basic requirement is that these metrics are easy to collect, it is also conducive to improving the testing process and the testing capability of the testing team, but it is important not to evaluate the individual abilities and performance of the testing personnel.

Transfer from: TestSoftware TestingNet [http://www.ltesting.net]
Link: http://www.ltesting.net/ceshi/ceshijishu/csyl/2012/1011/205600.html