CTFL-v4 Managing the Test Activities Practice Question
When should a test manager decide to stop the testing process?
⚠ Common exam trap
Students often fall for the trap of answering 'when all bugs are fixed' or 'when time runs out', ignoring that testing stops based on predefined, objective exit criteria.
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
✓
When the defined exit criteria are satisfied.
Testing should stop when the exit criteria defined in the test plan are met or when the project can no longer justify the cost of further testing. This balance is crucial; testing until every single bug is found is impossible and economically unfeasible. By using defined criteria, the manager provides a clear, defensible decision for when to release the product while acknowledging that some residual risk will always exist.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
When all test cases have been executed and passed.
Why it's wrong here
Expecting 100% pass rate on all cases is often unrealistic. Some cases may be blocked, and some may be minor non-critical failures. Using a strict 'all must pass' rule can delay releases indefinitely. Exit criteria should be defined in terms of risk, critical functionality, and business needs, not just binary completion.
- ✗
When the project budget is completely exhausted.
Why it's wrong here
Stopping just because the money is gone is a failure of project management, not a quality-based decision. If significant risks remain, the product shouldn't be released just because the budget is empty. A good test manager should monitor the budget throughout the lifecycle to prevent such an abrupt and irresponsible shutdown.
- ✓
When the defined exit criteria are satisfied.
Why this is correct
Exit criteria serve as the objective benchmark for project readiness. When these criteria are met, it indicates that the risk has been reduced to an acceptable level as agreed upon by stakeholders. This provides a clear, professional basis for concluding the testing phase and moving to the next project step.
- ✗
When the developers tell the test team to stop.
Why it's wrong here
Developers often want to release early, but the decision to stop testing must be based on quality, not developer requests. The test manager's responsibility is to provide an objective assessment of product risk. Allowing developers to dictate the end of testing ignores the role of independent quality assurance and testing oversight.
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.