Test Planning, Monitoring, Control and Reporting
This domain covers the management cycle that turns test objectives into a plan, tracks progress, takes corrective action and communicates status. Exam questions test plan content, estimation choices, meaningful metrics, and the difference between monitoring, control and reporting.
Planning
A test plan typically defines scope, objectives, test approach, test items, schedule, resources, risks, entry and exit criteria, and deliverables. Estimation can be expert-based, metrics-based, test-case-point or use-case-point based, or percentage distribution. Delphi and planning poker reduce individual bias. Scheduling must account for environment availability, dependencies and critical-path items.
Monitoring, control and reporting
Monitoring compares planned and actual effort, execution progress, pass/fail rates, defect find and fix rates, requirements and risk coverage, and defect density. Control converts findings into action: reprioritize, reallocate people, adjust scope, escalate or revise the exit forecast. Reporting has two main forms: status reports for current progress, blockers and risks, and summary reports for closure and lessons learned. Dashboards should suit the audience.
Worked example
At 60% execution, the pass rate is 70% and 15 high-severity payment defects remain open. Risk coverage for payment is below target. Control actions: pause low-risk reporting tests, assign a payments subject-matter expert, run defect triage, and report a revised exit forecast to the steering group. Reasoning: risk coverage, not raw execution percentage, drives the decision, and stakeholders need the forecast early.
Traps
Do not confuse monitoring with control. Do not report only pass/fail counts. Do not treat estimates as fixed commitments. Do not hide bad news until closure. Do not use metrics that no stakeholder can act on.