CTFL 5.3.1: Recall metrics used for testing
K1Syllabus section 5.3.1
3 original PrepBench practice questions for learning objective 5.3.1 of the CTFL 4.0 syllabus. Try the examples below and check each answer against its syllabus reference.
Practice questions
Question 1
Which of the following is an example of a test progress metric?
- Resource usage and the test effort spent so far
- The mean time to failure measured for the product
- The residual risk level remaining in the test object
- The number of test cases run and not run, and how many passed and failed
Show answer
- Resource usage and the test effort spent so farResource usage and test effort are project progress metrics.
- The mean time to failure measured for the productMean time to failure is a product quality metric.
- The residual risk level remaining in the test objectResidual risk level is a risk metric.
- Correct answer: The number of test cases run and not run, and how many passed and failedTest cases run, not run, passed and failed are test progress metrics.
Test progress metrics include test case implementation progress, test environment preparation progress, the number of test cases run and not run, passed and failed, and test execution time. Resource usage and test effort are project progress metrics, mean time to failure is a product quality metric, and residual risk level is a risk metric.
Syllabus section 5.3.1
Question 2
Which of the following is an example of a defect metric used in testing?
- Defect density and defect detection percentage
- The number of test cases run and not yet run
- The product's mean time to failure value
- The cost of testing and the cost of quality
Show answer
- Correct answer: Defect density and defect detection percentageDefect density and defect detection percentage are defect metrics.
- The number of test cases run and not yet runTest cases run and not run is a test progress metric, not a defect metric.
- The product's mean time to failure valueMean time to failure is a product quality metric, not a defect metric.
- The cost of testing and the cost of qualityCost of testing and cost of quality are cost metrics, not defect metrics.
Defect metrics include the number and priorities of defects found and fixed, defect density, and the defect detection percentage. The other options are, respectively, test progress metrics, product quality metrics, and cost metrics.
Syllabus section 5.3.1
Question 3
A test manager wants a metric showing how far the executed tests reach into the requirements and into the code. Which metric category provides this?
- Defect metrics, such as defect density and defect detection percentage
- Product quality metrics, such as availability and response time
- Test progress metrics, such as the number of test cases run and passed
- Coverage metrics, such as requirements coverage and code coverage
Show answer
- Defect metrics, such as defect density and defect detection percentageDefect metrics count and classify defects; they say nothing about how far the tests reach.
- Product quality metrics, such as availability and response timeProduct quality metrics describe the test object's behaviour, such as availability or response time.
- Test progress metrics, such as the number of test cases run and passedTest progress metrics track how much of the planned test work has been carried out.
- Correct answer: Coverage metrics, such as requirements coverage and code coverageRequirements coverage and code coverage are the listed coverage metrics.
Test metrics are gathered to show progress against the planned schedule and budget, the current quality of the test object, and the effectiveness of the test activities. Among the common test metrics, coverage metrics are the ones expressed as requirements coverage and code coverage, which is exactly what a reach-into-requirements-and-code measure needs.
Syllabus section 5.3.1
Original PrepBench practice material, not official exam questions or exam dumps. PrepBench is independent and is not affiliated with or endorsed by ISTQB®.