Measuring Software Testing
Someone has rightly said that if something cannot be measured, it can not be managed or improved. There is immense value in measurement, but you should always make sure that you get some value out of any measurement that you are doing. You should be able to answer the following questions:
* What is the purpose of this measurement program?
* What data items you are collecting and how you are reporting it?
* What is the correlation between the data and conclusion?
Any measurement program can be divided into two parts. The first part is to collect data, and the second is to prepare metrics/chart and analyse them to get the valuable insight which might help in decision making. Information collected during any measurement program can help in:
* Finding the relation between data points,
* Correlating cause and effect,
* Input for future planning.
Normally, any metric program involves certain steps which are repeated over a period of time. It starts with identifying what to measure. After the purpose is known, data can be collected and converted in to the metrics. Based on the analysis of these metrics appropriate action can be taken, and if necessary metrics can be refined and measurement goals can be adjusted for the better.
Data presented by testing team, together with their opinion, normally decides whether a product will go into market or not. So it becomes very important for test teams to present data and opinion in such a way that data looks meaningful to everyone, and decision can be taken based on the data presented.
Every testing projects should be measured for its schedule and the quality requirement for its release. There are lots of charts and metrics that we can use to track progress and measure the quality requirements of the release. We will discuss here some of the charts and the value addition that they bring to our product.
* Defect Finding Rate
* This chart gives information on how many defects are found across a given period. This can be tracked on a daily or weekly basis. Defect Fixing Rate
* This chart gives information on how many defects are being fixed on a daily/weekly basis. Defect distribution across components
* This chart gives information on how defects are distributed across various components of the system. Defect cause distribution chart
* This chart given information on the cause of defects. Closed defect distribution
* This chart gives information on how defects with closed status are distributed.Test case execution
* Traceability Matrics
* Functional Coverage
* Platform Matrics