How to measure test efficiency

I personally think that the following indicators in the software testing activities can be used to evaluate and measure the test efficiency. Each indicator is high and can naturally explain some problems:

1. DiscoveryDefect Quality:

In the same project team, we generally use the test management tool td to set each person's defects according to the priority and severity levels.Bar Chart and pie chartPut it in a document and send it to you to let the members in the group know their work conditions and others' work conditions. At the same time, developers are also asked to evaluate the work of each Tester for reference during performance appraisal. Especially testers who find very hidden defects must be rewarded.

2. TestedValidity:

In general, the effectiveness of submitting bugs reflects whether the tester can correctly understand the system, detect problems, and detect valid problems. In many cases, the tester fails to determine the requirement or the design. Once an exception occurs, the tester submits a bug. not the same as the previous defects, but the same type of defects are submitted repeatedly, that is, invalid bugs are submitted. As a result, many defects are rejected by the project during review, which delays the time, efficiency is naturally not high.

3. Test team membersCross-test, The number of missed test problems found:

This is often the case when a tester finishes testing and fixes all the defects. At this time, the testing module and the testing personnel may have a lot of problems. In this way, we can calculate the number of detected problems in the test. In this way, the testers are forced to perform each round of tests seriously, and they are not willing to slack off each test.

4.Missed customer DefectsRatio:

Once the version test is passed and released to the customer, the customer shall perform Acceptance Test on the released version. We will also find some problems. We will also allocate bugs found during the test to each module and specific persons. However, if the defect cannot be reproduced in the test environment and can only appear in the actual working environment, it is not a bug missed to the customer and is not included in the missed test statistics. Sometimes, the customer system will also find defects in use, and we should keep a record as well.

5. Number of defects submitted:

Within the same project group, the number of bugs submitted each day, the number of bugs submitted each week, and the number of bugs submitted after each version test is completed. The final test ends and calculates the percentage of valid defects each person submits.

6. Number of execution cases: [Allen]I personally think it is not desirable, because the efforts of different test cases will be different. The preliminary preparation and background knowledge are different.

The number of execution cases for each tester on the same day. However, you must remove functional modules that cannot be tested or blocked. Otherwise, your comments will increase!

7. speed and quality of Writing Test Documents:

Every time you write test cases, you need to write test cases for some modules. You can also write the number, speed, and quality of cases per unit time to differentiate the efficiency of each person, I think it is also a good method.

8. Efficiency of identifying issues during review: [Allen]Valuable review opinions should be put forward, and review should not be conducted for review

During case reviews within the Organization Department, if the same test document is reviewed, there are many suggestions for modification and it is of great reference value. The efficiency of such testers should be relatively high. You must consider salary increases.

9. Proficiency in testing tools:

Of course, a tester is more proficient in testing tools and more skillful in using them. Generally, the testing efficiency is higher. Generally speaking, it is impossible for everyone to understand all the automated testing tools. We only need to evaluate the commonly used testing tools. It is still user-friendly. In addition, our real goal is to train our colleagues who know more about the testing tools and quickly grasp the basic usage of the testing tools.

10. Test Result Analysis level: [Allen]This is very important. The analysis level shows the level of a person's testing level and understanding of product requirements.

For automated testing tools, especially after performance testing, we need to analyze some test results. If you are not familiar with the analysis of testing tools, what about efficiency? Therefore, the analysis level of the test results can also be used as an indicator to measure the test efficiency.

 

From: http://blog.csdn.net/fenfangnaicha/article/details/4404796