The test plan should include which of the following?

Scope, approach, resources, schedule and risks for the test activities — A test plan describes the scope, approach, resources, schedule, entry/exit criteria and risks associated with the test activities. (CTFL v4.0 – Section 5.1.1)

Entry criteria for a test level typically include:

Test environment ready, test data available, testable code delivered — Entry criteria describe what must be in place before testing can start — for example environment readiness, availability of test data, and delivery of testable code. (CTFL v4.0 – Section 5.1.3)

Which of the following is a RISK-based testing benefit?

It focuses test effort on the areas of highest product risk first — Risk-based testing prioritises test design and execution on the highest-risk items so that the most important risks are mitigated first. (CTFL v4.0 – Section 5.2)

Which of the following would MOST likely appear on a test progress report?

Number of test cases planned, executed, passed, failed, and remaining defects by severity — Test progress reports typically communicate test execution status, defect metrics, coverage, and outstanding risks. (CTFL v4.0 – Section 5.3)

Configuration management supports testing by:

Ensuring all test items are identified, version controlled, and traceable — Configuration management identifies, controls and tracks the versions of test items, test environments and testware so results are reproducible. (CTFL v4.0 – Section 5.4)

Which of the following BEST describes a defect report?

A record of an anomaly with steps, expected vs actual, severity and status — A defect report records an anomaly found in testing — including reproduction steps, expected vs actual results, severity, priority and status. (CTFL v4.0 – Section 5.5)

Estimation techniques used in test management include:

Expert-based (e.g., three-point estimation) and metrics-based (e.g., historical data) — ISTQB recognises expert-based estimation (e.g., three-point, Wideband Delphi) and metrics-based estimation (using historical productivity data) for test effort. (CTFL v4.0 – Section 5.1.4)

Which of the following is an example of a PRODUCT risk?

The payment feature fails to correctly calculate GST — Product risks relate to the quality of the product itself (e.g., a payment miscalculation). Project risks relate to project execution (staffing, environment, schedule). (CTFL v4.0 – Section 5.2)

Which of the following is typically part of the test strategy (as opposed to a specific test plan)?

The organisation's high-level approach to testing across projects — A test strategy defines a generic, high-level approach to testing at the organisation or programme level; the test plan applies it to a specific project. (CTFL v4.0 – Section 5.1.1)

An analytical test strategy is characterised by:

Testing based on analysis of a specific factor such as risk or requirements — An analytical test strategy bases test selection on analysis of a factor — most commonly risk (risk-based testing) or requirements. (CTFL v4.0 – Section 5.1.2)

Which is a valid exit criterion for stopping testing?

All planned tests executed, defect metrics within limits, remaining risks accepted — Typical exit criteria include: planned tests executed, coverage targets met, defect metrics within thresholds, and residual risks accepted by stakeholders. (CTFL v4.0 – Section 5.1.3)

Which is a metrics-based test estimation technique?

Estimation based on historical defect and productivity data — Metrics-based estimation uses historical data (past effort, defect densities, productivity) to derive estimates for the new project. (CTFL v4.0 – Section 5.1.4)

Which factor MOST directly affects test effort?

Product risk level, complexity, and quality of the test basis — Test effort is driven by factors like product characteristics (risk, complexity, size), quality of the test basis, tools, environment and team skills. (CTFL v4.0 – Section 5.1.5)

A risk level is typically calculated as:

Likelihood × impact — Risk level = likelihood of the risk occurring × impact if it does occur. Higher-risk items receive earlier and more thorough testing. (CTFL v4.0 – Section 5.2)

Which of the following is a PROJECT risk (as opposed to product risk)?

The environment might not be ready on time — Project risks relate to project execution (schedule, staffing, environment). Product risks relate to how the product might fail. (CTFL v4.0 – Section 5.2)

Which metric would BEST show test progress?

Number of test cases planned vs. executed vs. passed vs. failed — Test progress is typically shown via execution status: planned, executed, passed, failed and blocked test cases. (CTFL v4.0 – Section 5.3)

Which report is produced at the end of a test level or project?

Test summary report — A test summary report is produced at the end of a test level or project to summarise what was tested, results, remaining risks and lessons learned. (CTFL v4.0 – Section 5.3)

Which of the following is NOT a typical attribute of a good defect report?

The developer's home address — A good defect report is factual and product-focused: reproduction steps, expected/actual results, severity/priority, environment. Personal data is not appropriate. (CTFL v4.0 – Section 5.5)

Severity of a defect describes:

The impact of the defect on the product/user — Severity describes the impact of the defect on the product/user; priority describes how urgent it is to fix given business context. (CTFL v4.0 – Section 5.5)

A definition of done (DoD) in Agile typically acts as:

Exit criteria at the story/increment level — The Definition of Done in Agile acts as an exit criterion — a shared checklist that a story/increment must satisfy before being considered complete. (CTFL v4.0 – Section 5.1.3)

ISTQB · CTFL v4.0 · Chapter 5

ISTQB Chapter 5 Sample Questions – Managing Test Activities (CTFL v4.0 · 2026)

Chapter 5 covers the management side of testing: test planning, entry/exit criteria, test estimation, risk-based testing, test monitoring and control, configuration management, and defect management.

Twenty CTFL v4.0-style questions below — tap any question to reveal the correct answer, a plain-English explanation and a syllabus reference. Key terms link through to the ISTQB glossary.

Test plan Entry criteria Exit criteria Risk-based testing Defect report Configuration management