I85PREP
⌘ K
ISTQB CTAL-TM study materials
ISTQB CTAL-TM study resources

ISTQB CTAL-TM: Test Management in Context: Organizational Test Strategy and Test Approach

ISTQB CTAL-TM · Work through your exam, one topic at a time.

All guide sections

Test Management in Context: Organizational Test Strategy and Test Approach

This domain tests whether you can align testing with organizational strategy and choose a defensible project test approach. Questions often hinge on the distinction between test policy, organizational test strategy and the project test approach, and on which context factors drive each.

The hierarchy

  • Test policy: management's high-level principles, quality objectives and risk appetite for testing.
  • Organizational test strategy: generic, reusable rules for testing across projects, including common test levels, types, independence and documentation expectations.
  • Test approach: the project-specific implementation, selected and tailored from strategy elements.

Drivers and strategy types

Context factors include business domain, technical architecture, contractual and regulatory obligations, organizational constraints, and the chosen SDLC. Common strategy types are analytical (risk-based, requirements-based), methodical (checklists, quality characteristics), process-compliant (standards, maturity models), reactive (exploratory, session-based), consultative (expert or user-driven), and regression-averse (heavy automation).

Worked example

A regulated medical device is delivered under a fixed-price contract. The organizational strategy is process-compliant with ISO 29119 and safety standards, requiring traceability and formal reviews. The project test approach combines analytical risk-based system testing for high-risk safety functions with process-compliant review evidence. Exploratory testing is allowed for usability but not for safety requirements. Reasoning: the regulatory driver dominates, risk-based allocation focuses limited effort, and exploratory work is constrained by the need for audit evidence.

Traps

Do not treat test strategy and test approach as synonyms. Do not copy a corporate strategy unchanged into a project. Do not choose a purely reactive approach where audit evidence is mandatory. Do not ignore contractual or regulatory drivers when selecting test types.