CSTE -- 11. Status of Testing

11. Status of TestingMetrics specific to testing include data collected regarding testing, defect tracking, and software performance. Use quantitative measures and metrics to manage the planning, execution, and reporting of software testing, with focus on whether goals are being reached.

1. Test Completion Criteria
1. Code Coverage - Purpose, methods, and test coverage tools used for monitoring the execution of software and reporting on the degree of coverage at the statement, branch, or path level.
2. Requirement Coverage - Monitoring and reporting on the number of requirements exercised, and/or tested to be correctly implemented.
2. Test Metrics
1. Metrics Unique to Test - Includes metrics such as Defect Removal Efficiency, Defect Density, and Mean Time to Last Failure.
2. Complexity Measurements - Quantitative values accumulated by a predetermined method, which measure the complexity of a software product.
3. Size Measurements - Methods primarily developed for measuring the software size of information systems, such as lines of code, function points, and tokens. These are also effective in measuring software testing productivity.
4. Defect Measurements - Values associated with numbers or types of defects, usually related to system size, such as 'defects/1000 lines of code' or 'defects/100 function points'.
5. Product Measures - Measures of a product’s attributes such as performance, reliability, failure, usability,
3. Management By Fact - Management by fact is using quantitative measures and metrics to manage the planning, execution, and reporting of software testing.