A test plan organizes a body of testing; a test case specifies one check and the information needed to run and evaluate it. They work together: the plan sets the scope and approach, while cases make individual checks concrete.
What is the difference between a test plan and a test case?
| Dimension | Test plan | Test case |
|---|---|---|
| Main question | What testing will be done, how, by whom, with what resources, and on what schedule? | Given these preconditions and inputs, what action is taken and what result should occur? |
| Scope | A project, release, test level, or test type | One test objective or condition |
| Typical contents | Objectives and scope, approach, resources, schedule, tasks, responsibilities, environment, criteria, and risks | Preconditions, inputs, actions where applicable, expected results, and postconditions |
| Purpose | Coordinates and communicates intended testing | Makes a particular check executable and assessable |
| Relationship | May organize many test cases and may sit alongside more detailed plans | Under ISO/IEC/IEEE 29119-1:2022, the lowest level of test implementation documentation for its intended level or type |
The ISTQB Glossary defines a test plan as “A document describing the scope, approach, resources and schedule of intended test activities.” Its test-case definition includes preconditions, inputs, applicable actions, expected results, and postconditions. See the ISTQB test plan entry and the ISTQB test case entry.
What belongs in each artifact?
A test plan organizes the work
A plan usually makes clear what is in scope, how the team intends to test it, who will do the work, what resources and environment are needed, and when activities should happen. Depending on the project, it can also record test items and features, task owners, tester independence, test design techniques, entry and exit criteria, rationale, and risks. The appropriate level of detail depends on project context, size, and risk; a plan is not a universal fixed-form template.
ASTQB’s presentation of ISTQB Foundation Level syllabus section 5.1 says a test plan describes objectives, resources, and processes for a test project. Treat this as syllabus guidance, not a separate international standard: ASTQB, 5.1 Test Planning.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11A test case makes one check executable
A case gives a tester enough information to perform a particular check and judge its result. Include the relevant starting conditions, input data, action or actions, expected result, and any postcondition that matters. If the expected result is missing or vague, the tester may be able to perform an action but cannot reliably decide whether it passed.
ISO/IEC/IEEE 29119-1:2022 defines a test case as a set of preconditions, inputs, and expected results developed to drive execution of a test item toward test objectives; its inputs can include data and actions. The standard describes the case as the lowest level of test implementation documentation for its intended level or type. This is a standard definition, not a claim that the standard is legally mandatory or the only valid documentation approach. See ISO/IEC/IEEE 29119-1:2022.
How do they fit together?
The plan sets the context and coordinates a body of testing; cases carry out particular checks within that work. For example, a checkout release plan may identify payment integration as a risk and allocate testing time and a sandbox environment. Individual cases can then check successful payment, declined payment, and what happens when a payment response is delayed. A plan does not replace those executable checks, and a collection of cases alone does not explain the overall scope, schedule, responsibilities, or approach.
A project can use more than one plan: for example, a master plan plus plans for particular test levels or test types. The structure depends on the project’s needs; the ISO/IEC/IEEE 29119-1:2022 material describes this plan hierarchy.
Examples: checkout test plan and login test case
Illustrative test plan
The ISTQB Glossary’s checkout example illustrates how a plan can be framed. This is an example, not a required template:
- Scope: cart, payment, and order confirmation for an e-commerce checkout release.
- Approach: use risk-based testing for the payment integration.
- Resources and environment: assign two testers and use a sandbox payment gateway.
- Schedule: plan the work across three weeks.
- Exit criteria: define what must be satisfied before testing is considered complete.
These decisions tell the team what work to organize. They do not, by themselves, specify the steps and expected results of each checkout check. For the source example and the note that plan depth should fit project size and risk, see the ISTQB Glossary test plan entry.
Rank #4
Illustrative test case
The following login example is adapted from the ISTQB Glossary entry. The 16-character limit is specific to this illustration; it is not a general password rule:
- Preconditions: the account exists and the user is on the login page.
- Input: a password at the system’s allowed 16-character limit.
- Action: submit the login form.
- Expected result: login succeeds and the user is redirected to the dashboard.
- Postcondition: an authenticated session exists.
A companion boundary case can use a 17-character password and expect the system’s specified error message. The exact wording and behavior should come from the product requirements; the example does not establish a universal message. See the ISTQB test case entry.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Best Value
How to decide which one you need
- Use a test plan when the question is about the scope, approach, ownership, resources, timing, environment, or criteria for a body of testing.
- Use a test case when someone needs to execute a particular check and assess its result against an expectation.
- Use both when a team needs to coordinate testing and then perform traceable, repeatable checks.
- Scale the documentation to the project and its risks; workplace templates and the level of detail can vary.
Or skip the browser setup
If your test documentation includes capturing website states, ScreenshotNeo can return a screenshot or PDF with one GET request. Its clean-shot options accept consent banners like a visitor and remove 60+ known consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and responses identify page verdict and billing status in headers. An MCP server offers take_screenshot, get_page_info, and capture_pdf to AI agents and other MCP clients. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000. See the ScreenshotNeo documentation.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpFor this test-plan and test-case article, this is an optional way to capture a web page as supporting evidence, not a substitute for either testing artifact. Learn about ScreenshotNeo or sign up free for 1,000 screenshots a month with no card.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
