fbpx

MEASURING TESTER’S SUCCESS

08 Mar MEASURING TESTER’S SUCCESS

Measure-success

How to measure tester’s success is really a big challenge. Can tester’s ability be measured by number of defects logged? Answer is No, there are many other impacted areas which have more influence to measure tester’s success.

Type of Defect:

One needs to check the type of defect logged by each tester, many times tester’s log all issues in one issue and many times they prefer to log all the issues separately. If almost all logged issues are based on UI and customer is looking for functionality more than UI then this issues will have less weightage as compared with UI.

But if the company is like “Pixel Perfect” than in this case UI issues are having more weightage as compared with functional.

Issue Area:

Many times tester’s find issues which are least likely to be used. In current rapid development and release environment tester needs to understand the RISK involved in testing. They needs to prioritize their testing area and testing scope.

If tester gets more and more issues from the LOW RISK area and still issues are present in HIGH RISK area then issue weightage should be reconsidered.

Type of Testing Performed:

Issues found during regression would be lesser than the issues found during the first round of testing. So the type of testing should be considered during the issues weightage.

Complexity:

Issue complexity is one of the factors which should be considered while calculating the issue weightage, Issues which are easy to find should have less weightage as compared with issues found with more complexity.

 

If would be interested in Aware Testing Services, you can view our Testing Solutions Page.