Learn, Share and Keep Learning
| Software Testing - Measurement |
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:
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:
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.
This chart gives information on how many defects are found across a given period. This can be tracked on a daily or weekly basis. This chart gives information on how many defects are being fixed on a daily/weekly basis. This chart gives information on how defects are distributed across various components of the system. This chart given information on the cause of defects. This chart gives information on how defects with closed status are distributed. |