Types of Software Testing Metrics
Types of Software Testing Metrics
Software testing metrics are categorized into two primary types:
Process Metrics
Measure the efficiency and effectiveness of the testing process. Examples include test execution progress, defect detection rate, and resource utilization.
Product Metrics
Evaluate the quality of the software product. Examples include defect density, requirement coverage, and code complexity.
Base Metrics (Directly Measured)
Base metrics are raw, quantitative data collected directly during testing. Used to track daily progress and identify immediate issues.
- Total Test Cases Designed: Number of test cases created. Example: 150 test cases.
- Test Cases Executed: Number of tests run. Example: 140 executed.
- Test Cases Passed/Failed: Count of passed/failed tests. Example: 120 passed, 20 failed.
- Defects Found( Defect Count ) : Total defects identified. Example: 25 defects.
- Test Execution Time: Hours spent testing. Example: 50 hours.
- Lines of Code (LOC): The number of lines in the software code.
- Number of Requirements: The total count of requirements tested.
Derived Metrics (Calculated from Base Metrics)
Calculated using base metrics to evaluate trends, quality, and process efficiency. Help in decision-making and process improvement.
- Test Execution Pass Percentage: (Passed Tests / Executed Tests) * 100. Example: (120/140)*100 = 85.7%.
- Defect Density: Defects per size unit (e.g., KLOC). Example: 25 defects / 5 KLOC = 5 defects/KLOC.
- Test Effectiveness: (Defects Found During Testing / Total Defects Found) * 100. Example: (25/30)*100 = 83.3%.
- Defect Escape Rate: Defects found post-release vs. during testing. Example: 5 escaped defects / 30 total = 16.6%.
- Requirement Coverage: (Requirements Tested / Total Requirements) * 100. Example: 18/20 = 90%.