Home/ Techniques/ Test Lead/ Test Strategy
Test Lead · Management Technique

Test Strategy

Define the "How" for the whole organisation. A Test Strategy is the long-term, high-level approach that ensures consistency, efficiency, and quality across every project.

Test Lead ISTQB CTAL-TM Ch. 2 — K4 Create ~20 min read + exercise

1 The Hook — The Ship without a Compass

Imagine a fleet of 10 ships trying to reach an island. Every captain has their own map. One thinks they should avoid the reefs; another thinks they should sail right through them to save time. One uses a compass; another follows the stars. They'll never arrive together, and half of them will sink.

In a software company, your "projects" are the ships. Without a **Test Strategy**, every team tests differently. Some do automation, some don't. Some report bugs in Jira, others use Slack. The Test Strategy is the fleet's compass.

2 The Rule — Strategy vs. Policy vs. Plan

A Test Strategy defines the organisational approach, whereas a Test Plan defines the project-specific execution.

Document Scope Content
Test Policy Executive High-level goals (e.g. "We will be the most secure bank in NZ").
Test Strategy Organisation General methods (e.g. "We use Risk-Based Testing for all projects").
Test Plan Project Specific details (e.g. "John will test the Login page on Tuesday").

3 The Analogy — The Building Code

Analogy

The Code vs. The Blueprint.

The **NZ Building Code** (Test Strategy) says that every house must have fire-safe wiring and waterproof roofing. It doesn't tell you where the kitchen goes in *your* house. The **Architect's Blueprint** (Test Plan) shows exactly where the walls are for your specific home. You can't build a safe house without the Code, and you can't build a specific house without a Blueprint.

4 Watch Me Do It — NZ Fintech Strategy

Scenario: You're the Head of QA for a new NZ Fintech startup. You need to define the Strategy for the next 2 years.

  • Choose the Type: Analytical. We will use **Risk-Based Testing** because financial data is high-impact.
  • Define Levels: Unit (Devs), Integration (Testers), UAT (Business Users).
  • Tooling Standard: "All teams must use Playwright for Web and Postman for API. No exceptions." (This ensures people can move between teams easily).
  • Environment Strategy: "Dev -> Test -> UAT -> Prod. No testing in Prod."
  • Reporting Standard: "Weekly status reports must include the Risk Matrix and Defect Aging."

5 Decision Tool — Which Strategy Type?

🔍 Analytical (Risk-Based)

Best for: High-stakes apps (Banking, Health). Focuses on where the most damage can occur.

📋 Methodical (Checklist-Based)

Best for: Standard apps (E-commerce). Uses industry standards like ISO 25010 or internal checklists.

6 Common Mistakes

🚫 The "Dust Collector" Document

I used to think: I'll write a 50-page strategy so I look smart.
Actually: Nobody reads 50-page documents. A good strategy is 5-10 pages of **actionable constraints**. If the team isn't using it to make decisions, it's a failure.

🚫 Too much "Project Detail"

I used to think: I'll list the names of the testers in the strategy.
Actually: That belongs in the **Test Plan**. The Strategy should be project-independent. If you have to update the Strategy every time someone joins the team, it's not a Strategy.

7 Now You Try — Strategy or Plan?

🎯 Interactive Exercise

Scenario: You're reviewing a document. It says: "We will use the **V-Model** for all regulatory projects."

Is this statement part of a Strategy or a Plan?

Because it defines the approach for **ALL** projects of a certain type, it is a Strategy.

8 Self-Check

Q1. What is a "Regression-Averse" strategy?

It is a strategy that prioritises preventing existing features from breaking. It usually involves heavy automation and extensive "Sanity Checks" before every release.

Q2. Can a project deviate from the organisational Test Strategy?

Yes, but it must be **justified** in the Project Test Plan. For example: "The strategy says we use Playwright, but this project is a legacy Delphi app that Playwright doesn't support, so we will use Tool X instead."

9 Interview Prep

"How do you implement a new Test Strategy in an existing team?"

Answer: "I start with a **Gap Analysis** — what are we doing now vs. what the strategy requires? I don't force it all at once. I pick one 'Pilot' project to use the new strategy, gather feedback, and then roll it out to the rest of the organisation. A strategy is only effective if the team 'buys in' to the benefits."