Test Plan vs. Test Case: What's the Difference?

The Short Answer

A test plan is a planning document for a testing effort — usually a release. It sets the scope, approach, environments, schedule, people, and the criteria for calling testing done. A test case is a single check: preconditions, steps, and one expected result. A plan *selects and schedules* test cases; a test case *verifies* one behavior.

One test plan typically pulls in dozens to thousands of test cases. The same test case is usually reused by many plans over its life — every regression plan for every release, for example.

What Is a Test Plan?

A test plan answers the questions a release needs answered before testing starts: what is in scope (and what isn't), how it will be tested (manual, automated, exploratory, performance), where (which environments and devices), who is testing what, when, what risks could derail it, and what the entry and exit criteria are — the conditions for starting and for signing off.

It's written by a QA lead or test manager, reviewed with engineering and product, and updated if scope changes mid-release. Our test plan template walks through every section.

What Is a Test Case?

A test case is the smallest unit of testing work: a repeatable check that anyone can run and get the same answer. It has a title, preconditions, numbered steps, test data, and an expected result — and on each run it gets a status: pass, fail, blocked, or skipped. See how to write test cases for the fields and method.

Side-by-Side Comparison

A Worked Example

Test plan: Checkout redesign (v2.4). Scope: the new checkout flow and payment providers; the old account pages are out of scope. Approach: manual testing of the new flow, the automated regression suite on every build, a half-day exploratory session. Environments: staging, on Chrome, Safari, and iOS. Exit criteria: all critical and high test cases pass, no open critical bugs.

Among the test cases that plan pulls in:

1. Paying by saved card completes the order and shows a confirmation.
2. A declined card shows an error and leaves the cart intact.
3. A valid discount code updates the order total before payment.
4. An expired discount code is rejected.
5. Changing the shipping address recalculates tax.
6. Checkout works as a guest without creating an account.

The plan said *what matters for this release and when it's done*. The test cases are how each piece gets proved. When v2.5 comes, there'll be a new plan — and most of these same test cases will be in it.

How They Connect: Plan, Suite, Case, Run

• Test suites hold your test cases, grouped by feature. They're permanent.
• A test plan chooses suites and individual cases for one release, and sets the rules.
• Test runs execute the plan — often one run per environment — and record a result for every case.
• The release decision compares the runs' results against the plan's exit criteria.

This is the structure most test case management practices settle on, whether it lives in documents or a tool.

Test Plan vs. Test Strategy vs. Test Case

A test strategy sits one level above the plan. It sets the organization's or product's overall approach to testing — test levels, types, tools, automation goals, how defects are managed — and changes rarely. A test plan applies that strategy to one release; test cases carry it out.

Frequently Asked Questions