Software Testing Metrics

 Test metrics play a crucial role in software testing by providing quantitative and qualitative insights into the testing process and the quality of the software being developed. 

Why do we need Test Metrics?

Performance Measurement:

Test metrics help measure the performance and progress of the testing process. They provide data on test execution, test coverage, and defect status, allowing teams to assess their efficiency.

Quality Assessment:

Metrics such as defect density, defect leakage, and defect rejection ratio help assess the quality of the software. These metrics provide insights into the effectiveness of the testing process and identify areas that need improvement.

Resource Management:

Test metrics assist in resource management by helping teams understand how efficiently resources are utilized during testing. This includes tracking the number of executed, passed, and failed test cases, allowing teams to optimize their testing efforts.

Risk Identification:

Metrics highlight potential risks and issues in the software development and testing process. For example, a high defect density may indicate areas with a higher risk of defects, enabling teams to focus on critical areas.

Decision Making:

Test metrics provide data-driven insights for decision-making. Project managers, QA leads, and other stakeholders can make informed decisions based on metrics such as test coverage, defect trends, and test execution status.

Continuous Improvement:

Metrics are valuable for continuous improvement. By analyzing historical data, teams can identify patterns, trends, and areas for improvement in the testing process. This leads to more effective and efficient testing practices over time.

Communication and Reporting:

Metrics serve as a communication tool for various stakeholders. They provide a standardized way to communicate the status of testing efforts, allowing for transparent reporting and facilitating collaboration among team members.


Test metrics can be used for benchmarking against industry standards or best practices. By comparing metrics with established benchmarks, teams can identify areas where they excel and areas that may need improvement.

Goal Alignment:

Metrics help align testing activities with project goals and objectives. By tracking progress against predefined metrics, teams can ensure that testing efforts are aligned with the overall project and quality assurance objectives.

Efficiency Improvement:

Test metrics highlight bottlenecks, inefficiencies, or areas of improvement in the testing process. This allows teams to implement corrective actions and optimize their testing strategies for better efficiency.


  1. % of Test Cases Executed:

    • No. of Test Cases ExecutedTotal No. of Test Cases Written×100

  2. % of Test Cases NOT Executed:

    • No. of Test Cases NOT ExecutedTotal No. of Test Cases Written×100

  3. % Test Cases Passed:

    • No. of Test Cases PassedTotal Test Cases Executed×100

  4. % Test Cases Failed:

    • No. of Test Cases FailedTotal Test Cases Executed×100

  5. % Test Cases Blocked:

    • No. of Test Cases BlockedTotal Test Cases Executed×100

  6. Defect Density:

    • No. of Defects FoundSize (No. of Requirements)

  7. Defect Removal Efficiency (DRE):

    • Fixed DefectsFixed Defects + Missed Defects×100

      • A: Defects identified during testing or fixed
      • B: Defects identified by the customer or missed

  8. Defect Leakage:

    • No. of Defects Found in UATNo. of Defects Found in Testing×100

  9. Defect Rejection Ratio:

    • No. of Defects RejectedTotal No. of Defects Raised×100

  10. Defect Age:

    • Fixed Date - Reported Date
  11. Customer Satisfaction:

    • Measured by the number of complaints per period of time.