What changed
Apps now come in two modes. Testing mode is the runbook as it was. Live mode turns an app into a bug tracker: issues don't need a check, they take a priority and assignees, and a bug counts as fixed only once someone confirms the fix on the live app. A live app has an issue report you can open on screen or share as a link, a PDF, Excel, CSV or an email.
Plans come in from Excel, CSV and Markdown, and each of our downloadable templates imports the same way in every format. If your list has a shape of its own, in your own spreadsheet columns, a document or a pasted list, the AI import reads it with Claude into a preview. Nothing is saved until you've reviewed it, and your own check IDs are kept.
Connect GitHub or Linear and every issue gets a code like QA-12. A merged pull request that names it, in its title, description or branch, marks the issue fixed and asks the reporter to retest, either on merge or once it's deployed to an environment you choose. In Linear, moving the issue to Done does the same.
Why it matters
A fix nobody checks again is a guess. Tying the fix to the merge means the retest request goes out when the code lands, not when somebody remembers.
This was also the week paid plans arrived, and Free settled into what it is now: one person, one app and a monthly allowance of 150 checks tested, 30 issues and 2 AI imports, with every feature on. A check counts once a month however many platforms it's tested on, and a retest after a fix is free. At the limit only new work stops; everything already recorded stays readable, exportable and in reports.
Who it's for
Teams that already have a test list and don't want to start from nothing, and teams whose app is live and need somewhere for bugs to go.
For teams that want a hand getting started, we opened applications for the Founding 100: three months of Business free, with our help setting up the first test plan.
How to try it
Add an app and choose to start with AI, a template or an empty runbook. To move an existing app to live mode, use the mode switch in its settings. GitHub and Linear are in the app's Integrations tab.
What shipped
Bug tracking for live apps
Switch an app to live mode and it becomes a bug tracker: issues don't need a check, they take a priority and assignees, and a fix counts once someone confirms it. Share an issue report on screen, as a link, a PDF, Excel or CSV, or by email.
Import a plan from Excel, CSV or Markdown
Bring the test plan you already have. Upload a spreadsheet or a Markdown file, or let AI read your team's own test list into a runbook you review before anything is saved. Your own check IDs are kept.
Fixes from GitHub and Linear
Every issue gets a code, like QA-12. A merged pull request that names it marks the issue fixed and asks the reporter to retest, or waits until it's deployed. Linear works the same way: Done there means fixed here.
- GitHub
- Linear
The Founding 100
We're picking 100 software teams to get three months of qarunbook Business free, with our help setting up their first test plan.
Every change
New12
- Paid plans, and a Free plan of one person, one app and a monthly allowance (150 checks tested, 30 issues and 2 AI imports) with every feature on.
- Reports for every app: on screen, as a PDF, Excel or CSV, as a share link, or by email.
- A public REST API with workspace keys, documented at /docs.
- Zapier: triggers for new issues, fixes and results, and actions to record a result, raise an issue and mark it fixed.
- One Add button for a check, an issue, or many of either from a file. AI reads bugs in bulk, links each to its check and flags ones already open, and nothing is saved until you've reviewed it.
- Reporters are told in the app and by email when their issue is fixed.
- A viewer role, and roles per app.
- A partner program, with a dashboard for partners.
- Free templates to download as Excel, CSV or Markdown, a software testing checklist, a resources hub and a press kit.
- New guides: how to write test cases, login and checkout test cases, and retesting vs regression testing.
- Comparison pages for Zephyr, PractiTest and spreadsheets.
- Cursor and Codex can install the qarunbook plugin, as Claude Code can.
Improved8
- App cards show how complete each app is, and how many issues are open.
- Adding an app is one step: start with AI, a template or an empty runbook.
- Billing, API keys and Profile open from the sidebar as settings views.
- Every password field has a show and hide button.
- Reports and their PDFs show who tested each platform.
- Failing a check asks why, and the issue starts on the platforms that failed.
- Free workspaces are emailed when an allowance reaches 80% and when it's used up.
- The site's top bar has Use cases and Resources menus, so guides and tools are easy to find.
Fixed4
- Files attached while raising an issue on a live app show straight away, not after a reload.
- Leaving the report no longer crashes the page.
- Results and issues recorded over MCP carry the name of the person who owns the token.
- An imported app's name is checked only against your own workspace.