WinningKPI - Software Development/Quality - KPI for Measuring of Test Coverage % of Software Specifications posted in category Software Development/Quality KPI details: Details:
This indicator is for measuring what % of software specifications is tested before release.
Although testing software specifications incurs a cost for the company, the effort spent on this may be key to the quality of the products released.
Managers that scored low in Software Quality KPIs may choose to look at this KPI and identify whether higher test coverage will increase quality performance (for e.g. increase % of bugs found in house or the Defect Removal Efficiency).
The test coverage % can also be used in promotional campaigns (if high) and when closing deals.
Formula:
Total no. of software specifications covered in quality tests/ Total no. of software specifications x 100
KPI Units: %
KPI Time Frame: update quarterly or at the end of product release
Posted by Oana Boteanu | Help to protect community: Flag for moderation
Ideas suggested by WinningKPI community:Here are comments:
The test coverage % is a key element of quality and defect removal. For instance, it is unlikely that the DRE % (Defect Removal Efficiency) will be high if the test coverage is low.
For the developers to find the errors in house, they need to test it.
Example of poor test coverage:
Total number of software specifications: 20
Total number of software specifications tested: 10
10/20 x100 = 50 %
50% covers only half of the software specifications, leaving the other half of the specifications possibly loaded with bugs.
Oana Boteanu | + | September 11, 2012 at 7:50 am
×
Have something to add? Have some more thoughts? Help others and earn 5 credits!
×
Sign in to comment Please, register (there is a button 'Become a member of WinningKPI community') in the right sidebar or sign in to leave comments. It is free and more - you will have scores for each comment you post.
Articles in Software Development/Quality category:Relevant articles:
|