Templates

Test plan templates.Ready to use, free to take.

Knowing what to test shouldn’t be harder than testing it. Start from a plan that already has the checks in it, each with steps and the result to expect. Use it as a spreadsheet, or import it into qarunbook and work through it with your team.

01Templates
8

Release, retest, mobile, UAT, example test cases, login, checkout, and a blank one to fill in.

02Checks
146

Each with steps and the result you should see.

03Formats
3

Excel, CSV and Markdown. Take whichever you work in.

04Price
Free

No email and no sign-up to download.

Pick a starting point.Every one is a real plan.

Each template is written the way qarunbook imports it: a heading per section, one row per check, and a column for each platform.

Download it in the format you work in. Nothing to fill in first.

01Template

Release checklist

16 checks · 4 sections · Web, Android, iOS

A short pass to run before you ship an update: check every fix from last round, test what changed and the screen it sits on, run the paths that must never break, and finish with the ship checks.

  • Fixes from last round FIX2 checks
  • What changed CHG3 checks
  • Never ship broken CORE6 checks
  • Before you press publish SHIP5 checks
02Template

Retest log

13 checks · 3 sections · Web, Android, iOS

For confirming fixes: each reported bug checked again on the platform it was reported on, the screen around it, and a short never-break group to run after the fixes.

  • Fixes to confirm FIX4 checks
  • Around each fix NEAR3 checks
  • Never break CORE6 checks
03Template

Mobile app testing checklist

21 checks · 5 sections · Android, iOS

The things a web-shaped plan misses on Android and iOS: permissions, interruptions like calls and backgrounding, bad networks, small screens and large text, and upgrading over the last version.

  • First run and permissions ONB5 checks
  • Interruptions and state INT5 checks
  • Network NET4 checks
  • Devices and display DEV4 checks
  • Updates and store REL3 checks
04Template

Example test cases

13 checks · 5 sections · Web, Android, iOS

Worked test cases for the journeys most apps share: sign-up, password reset, checkout, going offline and permissions. Each one has what must be true first, numbered steps and the result to expect.

  • Sign up SIGN3 checks
  • Password reset RESET3 checks
  • Checkout PAY3 checks
  • Offline NET2 checks
  • Permissions PERM2 checks
05Template

Checkout test cases

35 checks · 5 sections · Web, Android, iOS

The money paths of a shop or a paid app: totals and discount codes, guest checkout, declined cards, 3-D Secure, Pay tapped twice, a dropped connection, refunds and receipts, Apple Pay, Google Pay and in-app purchases. Every card is a published test card.

  • Basket and totals CART7 checks
  • Address and account ADDR4 checks
  • Payment PAY13 checks
  • Interruptions and network NET5 checks
  • After the order ORDER6 checks
06Template

Login page test cases

30 checks · 8 sections · Web, Android, iOS

Thirty test cases for signing in: wrong passwords, lockout, staying signed in, password reset, Google and Apple sign-in, two-step codes, accessibility, and the phone-only cases like face or fingerprint sign-in.

  • Sign in AUTH6 checks
  • Password field and lockout LOCK2 checks
  • Staying signed in SESS5 checks
  • Forgot password RESET3 checks
  • Single sign-on and social sign-in SSO4 checks
  • Two-step verification MFA3 checks
  • Accessibility ACC3 checks
  • On a phone MOB4 checks
07Template

UAT test plan

13 checks · 4 sections · Web, Android, iOS

A worked example of a full test plan for a rideshare app, written the way user acceptance testing needs it: a journey per check, what has to be true first, steps anyone can follow, and the result to expect.

  • Sign up and sign in AUTH4 checks
  • Booking a ride RIDE4 checks
  • Payments PAY3 checks
  • Notifications PUSH2 checks
08Template

Blank import template

5 checks · 2 sections · Web, Android, iOS

The smallest plan that shows the format: two sections and a handful of checks. Replace the rows with your own and upload it as a new app.

  • Sign in AUTH3 checks
  • Checkout PAY2 checks

Rather have it by email?

Optional. We’ll send the template’s download links, so it’s in your inbox when you need it.

You’ll get the file, plus occasional product news. Unsubscribe any time. See the privacy policy.

Import one,and it becomes a runbook.

A spreadsheet tells you what to test. It doesn't tell you who tested it, on which platform, or whether the fix was ever checked again.

Import a template into qarunbook and each check gets a result on every platform, with a name against it.

01Step

Create a free workspace

No card needed. You can download the templates without one; you only need it to work through them here.

02Step

Add an app and choose “Use our template”

Upload the file — Excel, CSV or Markdown, whichever you edited. It is read exactly as written, with no AI and nothing guessed.

03Step

Work through it

Every check becomes a row with a result for each platform. Issues stay on the check that found them, and a fix waits for a retest before it counts as a pass.

Writing your own? Keep the same shape: a heading per section with its reference in brackets, like Sign in (AUTH), then the columns ID, Journey, Preconditions, Steps and Expected result, and one column per platform — WEB, AND, IOS. Write N/A where a check doesn’t apply. The blank import template is the shortest example.

Questions,answered.

Not sure where to start? The software testing checklist puts the release and mobile checks on one page, and the guides explain each template.

Do I need an account to download a template?
No. The download buttons are plain links to the files. You only need a workspace if you want to import a template and work through it in qarunbook.
Which format should I take?
Whichever you will edit in. Excel and CSV give one row per check with the section in the first column; Markdown keeps a heading per section. All three import the same way.
Can I change the checks before importing?
Yes, and you should. The templates are starting points: rename sections, delete checks that don't fit, add your own, and remove the platform columns your app doesn't ship to.
Does qarunbook run these tests for me?
No. qarunbook is where the plan, the results and the follow-up live. People work through the checks, and AI assistants connected over MCP can record results too. It does not run automated tests.
Is qarunbook free?
There is a free plan, with no card required. Paid plans raise the limits on apps, members and storage.

Start from a template.Finish with every check done.

Create a workspace, add your app, and upload the template you downloaded.

Free plan available — no card required.

Works with your AI and every platform you ship to

Claude
Codex
Cursor
Any MCP client
Web
Android
iOS