Software Testing

Beginner path · lesson 16 of 35

BeginnerStrategy4 min readPublished November 12, 2026

What is a test case? A test plan? A test strategy?

Three documents testers talk about all the time, at three different heights: the overall approach, the plan for one project and the single check. Here's what each one is and how they fit together.

On this page

Key takeaways

  • A test strategy is the general approach to testing, usually for a whole product or organisation: how we test here.
  • A test plan applies that approach to one project or release: what we'll test, how, when, by whom and when we're done.
  • A test case is one specific check: do these steps with this data and expect this result.

Three heights of the same work

Think of a trip.

  • The strategy is your general travel policy: "we travel by train when possible and always book refundable tickets."
  • The plan is this trip: dates, route, budget, what could go wrong.
  • The test cases are the checklist items: "passport in bag", "tickets printed".

Strategy is the widest view, test cases the narrowest. Each one guides the next.

Test strategy: how we test here

A test strategy describes the overall approach. It changes rarely and applies across many projects.

It usually covers:

  • Test levels and types used: unit, integration, system, acceptance; functional, performance, security.
  • How much to automate, and with which tools.
  • How risk guides testing: what gets tested most deeply.
  • Environments and test data: where tests run, and with what data.
  • Defect management: how bugs are reported, classified and tracked.

Test plan: this project, this release

A test plan applies the strategy to one project, release or feature. It answers practical questions:

SectionQuestion
ScopeWhat will we test, and what won't we?
ObjectivesWhat do we want to find out?
ApproachWhich levels, types and techniques?
ResourcesWho tests, with which tools and environments?
ScheduleWhen does testing happen?
Entry and exit criteriaWhen can we start? When are we done?
RisksWhat could go wrong, and what will we do about it?

In Agile teams, the test plan is often short: a page on a wiki, or part of the sprint planning. A plan doesn't have to be long. It has to be agreed on.

Test case: one specific check

A test case is the smallest unit. It describes one check precisely enough that anyone could run it and get the same verdict.

A typical test case contains:

  • ID and title: "TC-042: Login fails with a wrong password".
  • Preconditions: "A user ana@example.com exists".
  • Steps: what to do.
  • Test data: the exact values to use.
  • Expected result: what should happen.

You'll also hear test scenario (a broader situation to test, such as "user resets their password"), which usually contains several test cases. A test suite is a group of test cases run together, such as "checkout regression suite".

How they fit together

Real-world exampleLaunching gift cards at an online shop

Strategy (the shop's, written last year): risk-based testing; every critical flow has automated end-to-end tests; payment changes always get a security review.

Plan (for the gift card release):

  • In scope: buying, redeeming and checking the balance of gift cards.
  • Out of scope: the warehouse system, which is unchanged.
  • Payment is high risk, so a security review is planned in week 2.
  • Exit criteria: no open critical bugs; all high-risk test cases pass.

Test cases (a few of the 40):

  • TC-101: Redeem a gift card that fully covers the order total.
  • TC-102: Redeem a card with less balance than the order total; pay the rest by card.
  • TC-103: Try to redeem an expired gift card; expect a clear error.

Lesson: the strategy told the team payment is risky. The plan turned that into a security review and focused tests. The test cases made it concrete.

Check yourself

Your manager asks: 'When will testing of the new release be done, and what are we not testing?' Which document should answer that?

Show answer

The test plan. Schedule, exit criteria and scope, including what's out of scope, are exactly what a test plan is for.