Guides

How to work out what needs testing, write it so anyone can follow it, and get it tested. Every guide ends with a template you can copy and import.

• Bug report templateEvery field a developer needs to fix a bug the first time, weak reports rewritten into strong ones, and a template you can copy.
• Test case examplesThe test case format field by field, scenarios broken into cases, and sample test cases for search, forms, profiles, uploads and notifications.
• GitHub issue template for bug reportsA ready-to-copy issue form and Markdown template for .github/ISSUE_TEMPLATE, and how to make sure the fix gets checked again.
• Website testing checklistWhat to check on a website or web app before it ships: forms, links, layouts, browsers, sign-in, speed, accessibility and the emails it sends.
• How to write test casesStep by step, with worked examples for sign-up, password reset, checkout, offline and permissions, and a template you can copy.
• Retesting vs regression testingWhat each one checks, when it happens, a side-by-side table, and how to make sure a fix is checked again before it counts as passed.
• Test cases for checkout and payment35 checks for the money paths: declined cards, 3-D Secure, Pay tapped twice, a dropped connection, refunds, receipts, Apple Pay, Google Pay and in-app purchases.
• Test cases for a login pageThirty login test cases to copy, each with preconditions, steps and an expected result, from wrong passwords to two-step codes and face sign-in.
• UAT test plan templateThe columns that matter, worked examples of expected results, and a plan you can copy and import.
• Mobile app testing checklistWhat to check on iOS and Android that a web-shaped test plan always misses — permissions, interruptions, offline, updates.
• What to test before you ship an updateA short pass that catches the things that break between builds, without retesting everything.
• A QA MCP serverConnect Claude, Cursor or Codex to the runbook: read what is failing, fix it, and send the fix back for a retest.
• A QA skill for Claude CodeThe connection and the skill file that make Claude Code work the testing board the same way every time.

Also here

• Test plan templatesEvery template from these guides in one place, as Excel, CSV or Markdown, plus a blank one to fill in.
• Software testing checklistThe release and mobile checks on one page, each with steps and the result to expect.
• Testing apps built with AILet your assistant draft the plan and work the runbook over MCP, with a person still confirming every fix.
• For software agenciesA runbook per client app, and a report the client can open to see what was tested.
• Test plan gap checkerPaste a plan and see what it forgot. Runs in your browser, nothing uploaded.
• Free test case management, comparedWhat each tool’s free tier really gives you, read off their own pricing pages.
• Looking for a TestRail alternativeWhat TestRail costs, what its entry tier leaves out, and when it is still the right answer.
• Looking for a Qase alternativeWhere Qase’s free tier runs out, and what you gain and lose by moving.
• Looking for a Zephyr alternativeWhether your testing belongs inside Jira, and when a separate board is the better fit.
• Looking for a PractiTest alternativeWhat PractiTest is built and priced for, and what a smaller team needs instead.
• Test cases in Excel or Google SheetsWhen a spreadsheet is the right test plan, and the point where it stops being enough.

qarunbook turns any of these into a board your team and your AI share. Free to start.