Guide · updated 9 November 2026

Test plan template

A test plan is the list of everything a person should check before a release, and what they should see when they do. Here is what goes in one, a worked example, and a template you can copy or download.

There is an old rule: measure five times, cut once. Most teams building apps do the opposite. They build, push it out, and hope to catch whatever they catch on the way. When we went looking for a checklist we could use for our own apps, there was no single place that had one. Every app needs its own, so you have to write it. Most small teams don't have a professional tester to do that for them, so this page gives you the shape and a worked example to start from.

What goes in a test plan

Formal templates (the IEEE 829 kind) open with pages of scope, approach, risks, roles and schedules. For a small team, one short paragraph covers all of that: what build this is, which platforms, who tests, and when it has to be done. Everything else is the list of checks, and that list is the part that finds bugs.

Group the checks by area of the app: sign-in, the main journey, payments, forms, devices. Give each section a short code in brackets, so every check gets an ID like BOOK-03 that people can quote in a bug report.

The five columns every check needs

  • ID: the section code and a number. It never changes, even when the wording does.
  • Journey: what the user is trying to do, in their words. “Book a free slot”, not “POST /bookings”.
  • Preconditions: what must be true before the first step, such as an account, a role, a test card or no network.
  • Steps: numbered, one action each, written so someone who has never seen the app can follow them.
  • Expected result: what the user should see, specific enough that two people would agree on pass or fail. “Works” is not an expected result.

Then one column per platform (web, Android, iOS) for the result. A check can pass on web and fail on iOS; a single Status column hides that. Write N/A where a check does not apply, such as push notifications on web. (More on writing each check in how to write test cases.)

Test the paths people don't take on purpose

Most plans only check that the app works when people do exactly what the builder expected. The checks that find bugs are the others: a wrong password, a declined card, Confirm tapped twice, an empty account, no network, a member opening an admin page by its address. Give each section at least one of these. The example below has them in every group.

The template

A worked test plan for a booking app on web, Android and iOS. Copy it, or download it, and replace the rows with your own journeys.

test-plan-template.md
# Booking app — test plan

## Sign up and sign in (AUTH)

| ID | Journey | Preconditions | Steps | Expected result | WEB | AND | IOS |
|---|---|---|---|---|---|---|---|
| AUTH-01 | Sign up with an email address | No account for this email | 1. Open the app. 2. Tap Create account. 3. Enter a name, email and password. 4. Submit. | The account is created and the home screen opens. A verification email arrives within a minute. | | | |
| AUTH-02 | Wrong password shows a clear error | An existing account | 1. Enter the right email and a wrong password. 2. Tap Sign in. | A message says the email or password is wrong. The email stays filled in. | | | |
| AUTH-03 | Reset a forgotten password | An existing account | 1. Tap Forgot password. 2. Enter the email. 3. Open the link in the email. 4. Set a new password. | The new password signs you in. The old one no longer works. | | | |
| AUTH-04 | A lesser role cannot reach admin screens | A member account, not an admin | 1. Sign in as the member. 2. Open an admin page by its address. | Access is refused, and no admin data is shown. | | | |

## The main journey (BOOK)

| ID | Journey | Preconditions | Steps | Expected result | WEB | AND | IOS |
|---|---|---|---|---|---|---|---|
| BOOK-01 | Book a free slot | Signed in, a slot open tomorrow | 1. Open Book. 2. Pick tomorrow. 3. Pick the open slot. 4. Confirm. | The booking appears in My bookings with the right date and time, and a confirmation email arrives. | | | |
| BOOK-02 | A taken slot cannot be booked twice | A slot another account has just booked | 1. Try to book the same slot. | The slot shows as taken. No second booking is made. | | | |
| BOOK-03 | Confirm tapped twice | Signed in, a slot picked | 1. Tap Confirm twice quickly. | One booking is made, not two. | | | |
| BOOK-04 | Cancel a booking | An upcoming booking | 1. Open it. 2. Tap Cancel. 3. Confirm. | The booking is gone from My bookings, the slot is free again, and an email says so. | | | |
| BOOK-05 | An empty account | A new account with no bookings | 1. Open My bookings. | A message says there are no bookings yet, with a button to make one. | | | |

## Payments (PAY)

| ID | Journey | Preconditions | Steps | Expected result | WEB | AND | IOS |
|---|---|---|---|---|---|---|---|
| PAY-01 | Pay with a card | A paid slot picked, test card 4242 4242 4242 4242 | 1. Confirm. 2. Pay with the card. | The payment succeeds once, the booking is confirmed, and a receipt arrives. | | | |
| PAY-02 | A declined card is handled | A paid slot picked, test card 4000 0000 0000 0002 | 1. Pay with the declining card. | A message says the card was declined. No booking is made and the slot stays open. | | | |
| PAY-03 | Refund on cancel | A paid booking inside the refund window | 1. Cancel it. | The refund shows on the receipt, and the amount matches what was paid. | | | |

## Forms and errors (FORM)

| ID | Journey | Preconditions | Steps | Expected result | WEB | AND | IOS |
|---|---|---|---|---|---|---|---|
| FORM-01 | Empty and wrong input | The profile form open | 1. Save it empty. 2. Enter a wrong email format and very long text. 3. Save. | A clear message beside each wrong field. Nothing is saved half-way. | | | |
| FORM-02 | Changes survive a reload | The profile form open | 1. Change the name. 2. Save. 3. Reload or reopen the app. | The new name is still there. | | | |
| FORM-03 | No connection | Network cut | 1. Try to book or save. | A message says there is no connection. Nothing is lost, and it works once the network is back. | | | |

## Devices and notifications (DEV)

| ID | Journey | Preconditions | Steps | Expected result | WEB | AND | IOS |
|---|---|---|---|---|---|---|---|
| DEV-01 | Reminder before a booking | A booking in one hour, notifications allowed | 1. Wait for the reminder. | A notification arrives, and tapping it opens the booking. | N/A | | |
| DEV-02 | The smallest screen | Smallest supported phone or a narrow browser | 1. Open Book, My bookings and Profile. | Nothing overlaps or is cut off, and every button can be tapped. | | | |
| DEV-03 | Upgrade over the last version | The previous version installed, signed in | 1. Install this build over it. | Still signed in, bookings intact, no crash on first open. | N/A | | |

Or take the file: Markdown·CSV·Excel·no email, no sign-up.

Keep it short enough to finish

A plan nobody finishes tests nothing. For most small apps, 20 to 60 checks covers every journey. Before each release you don't need to rerun all of it: retest what was fixed, test what changed and the screen around it, and run the few paths that must never break. That shorter pass is in the release checklist and the regression testing checklist. If real users will sign off the build, the UAT test plan template is written for them.

Let AI write the first draft

If you build with Claude Code, Cursor or Codex, the AI can read every screen and route and write this list for you. Give it the table format above and ask for one check per journey. AI builds and builds and misses some parts; an inventory like this is what lets it switch to testing. The QA skill for Claude Code does exactly this, and how to test code written by Claude Code covers what to check once it has.

Run the plan without a second spreadsheet

A test plan in a spreadsheet goes stale once testing starts: results in one tab, bugs in a tracker, and no record of which fix was checked again. Import this template into qarunbook and every check gets a result per platform, issues are raised against the check they came from, and a fixed bug goes back for a retest instead of straight to passed. Free for one app, no card.