CTFL-v4 Managing the Test Activities Practice Question
Which of the following metrics would be most useful for a Test Manager to report the effectiveness of the testing process to stakeholders?
⚠ Common exam trap
Candidates frequently confuse test effectiveness metrics with productivity metrics like total tests executed or test velocity, overlooking quality and defect leakage aspects.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Defect detection percentage.
Measuring test effectiveness requires evaluating the quality of the tests themselves, not just the quantity of work. Defect detection percentage, or defect removal efficiency, provides a direct view of how many bugs were found during testing versus those found by end-users. This metric is critical for demonstrating the value of testing activities to business stakeholders who are concerned about software reliability and risk.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Number of test cases written per week.
Why it's wrong here
This is a productivity metric, not an effectiveness metric. It measures how busy the team is, but it tells the stakeholders nothing about the quality of the software or the ability of the test suite to find defects. It is easily manipulated and does not demonstrate real value.
- ✓
Defect detection percentage.
Why this is correct
Defect detection percentage (DDP) compares bugs found in testing to total bugs found (including those in production). A high DDP indicates that the testing process is highly effective at uncovering issues before release, which is the primary goal of testing and a key indicator for stakeholders.
- ✗
Total number of test cases executed.
Why it's wrong here
The number of executed test cases indicates progress, not effectiveness. Executing thousands of test cases is meaningless if they are poorly designed and fail to uncover critical defects. Stakeholders care about software stability, which is better measured by defect-related metrics than simple execution counts of test cases.
- ✗
Average number of hours per test case.
Why it's wrong here
This is a cost or efficiency metric, not an effectiveness metric. While it might help with future budget planning, it does not provide any insight into whether the testing process is successfully identifying risks or improving the overall quality of the software being delivered to the customer.
About these practice questions
Courseiva writes every CTFL-v4 question from scratch — 144 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official ISTQB exam blueprint
This CTFL-v4 practice question is part of Courseiva's free ISTQB certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CTFL-v4 exam.