QAM Hub QAM Hub
Home / Features / Checklists / Checklists

Checklist testing tool for QA teams

Spreadsheet-style QA checklists with a column per browser, device or build, keyboard-fast entry, a history for every cell and runs that lock as records when they are done.

A checklist testing tool does one job: let a tester run down a list of checks fast, mark each one Passed, Failed, Blocked or Skipped, and leave a record someone else can trust later. Most QA teams do this in a spreadsheet, because a spreadsheet is fast and nobody has to learn it. QAM Hub checklists keep that speed, a list of checks down the side and a column per browser, device or build across the top, and add what the spreadsheet silently loses: who set a cell, when, why, and the certainty that a finished run will still say the same thing next year. Checklists live in the same project as your test cases, automation results and requirements, so the lightweight tool and the structured one are the same tool.

What QA teams run as checklists

Checklists suit any test you can describe in one line to a tester who already knows the product. The typical lists teams move out of spreadsheets:

  • Smoke test checklist for every build or deploy: the same twenty checks, run on each environment, with a column per environment.
  • Cross-browser and device testing: one column per browser or device, so Chrome, Safari, Firefox and two phones sit side by side and the gaps are visible at a glance.
  • Release and go-live checklist for sign-off: the record a release manager reads once and never wants edited again.
  • User acceptance testing (UAT): a plain list business users can tick without learning steps and expected results.
  • Exploratory testing charters: areas to cover and risks to probe, with notes and bugs attached as the session goes.
  • Manual regression sweeps of areas that are too simple for full test cases but too important to skip.
  • Hardware, firmware and accessibility checks that are repeated on every revision.

Write a checklist as fast as a spreadsheet

A check is one line: a title and an optional note with the details. Checks sit in groups and sub-groups, carry tags, and get a project-wide number that is never reused, so "check 042" means the same thing in every run and every report.

  • Inline add: type a check at the bottom of a group, press Enter, type the next one.
  • Drag and drop between groups; moving a check does not touch the runs that already use it.
  • Bulk actions on a selection: move, duplicate, tag, delete, copy or move to another checklist suite.
  • CSV import and export with the columns Group, Check, Tags, Note, so an existing Google Sheets or Excel checklist moves over in minutes; nested groups are written as "Auth > Login".
  • AI-generated checks from a feature description or acceptance criteria, reviewed before they are added.
  • Checklists can also be read and written by Claude or another AI agent through the MCP server.

Run it as a grid: one column per browser, device or build

Starting a run turns the suite into a table: checks down the side, one column per browser, device, environment or tester across the top. Columns are added when the run is created or later, and a column can be scoped to a tag, so a "Safari" column only asks for the checks that matter in Safari. New checks added to the suite can join a running checklist automatically.

  • Four statuses per cell: Passed, Failed, Blocked, Skipped.
  • Keyboard entry: click into the grid, move with the arrow keys, press P, F, B or S, and the cursor advances on its own.
  • Bulk entry: select checks or a whole group and set a status for all of them in one go.
  • A comment on any cell, and a bug on any failed cell: create an issue in Jira, GitHub, GitLab, Linear, Asana, Redmine, Trello, Azure DevOps, ClickUp, YouTrack, Shortcut or ServiceNow, link an existing one or type its id. Several bugs can hang on one cell. See defect tracking.
  • Filters for Untested, Passed, Failed, Blocked, Skipped, With notes and With bugs, plus search by name or number.
  • Run Mode shows one check at a time for a tester walking through the list on a second screen or a phone.
  • Per-column progress and a pass rate for the whole run, visible from the Runs list without opening it.

A record your release review can trust

Every cell change is appended to a history with the status, the comment, who made it and when. The run keeps its own copy of each check's title and group, so renaming or deleting a check later never rewrites what was tested. When a run is marked complete it locks: nothing in it can change until someone deliberately reopens it. That is the difference between a QA checklist and a spreadsheet tab somebody edited in March.

Checklists and test cases in one place

A checklist-only tool is a good fit until the first feature that needs real steps and expected results, the first automated suite whose results should land next to the manual ones, or the first auditor who asks which requirement a check covers. In QAM Hub a checklist suite and a test case suite are two suite types in the same project. They share tags, custom fields, the bug tracker connection, milestones and reports, and both appear in the same Runs list. Teams start with checklists and add test cases, automation and requirements when they need them, without changing tools.

Checklist results show up wherever the rest of your testing does:

  • On the Runs page next to test runs, with their own type badge and pass rate.
  • In milestones: a checklist run attached to a milestone counts toward its readiness and burndown.
  • On the project dashboard, in the Manual Runs report and in the Defects report, which lists bugs filed from checklist cells.
  • In organization-wide reports and Projects Health, with an "Include checklists" switch for teams that want test-run numbers only.
  • As PDF or CSV of a single run, for the people who will never log in.

Spreadsheet, checklist-only tool or QAM Hub

What you needGoogle Sheets or ExcelChecklist-only toolQAM Hub checklists
A column per browser, device or buildYes, by handYesYes, including columns scoped to a tag
Who changed a cell, when and whyVersion history at file level onlyDepends on the toolPer-cell history with comment and author
A finished run that cannot be edited by accidentNoDepends on the toolCompleted runs lock until reopened
A bug in Jira or GitHub from a failed checkPaste a linkUsually a link fieldCreate or link the issue from the cell; it appears in the Defects report
Full test cases with steps and expected resultsAnother sheetNoSame project, same runs list
Automation results next to manual onesNoNoPlaywright, Cypress and JUnit XML imports linked to cases
Requirements and release readinessNoNoMilestones, burndown, traceability
Generate checks with AINoRarelyYes, reviewed before they are added

If you are comparing lightweight tools such as Testpad, the checklist part of the job is the same here: a fast list, a grid per run, keyboard entry, bugs from a cell. The difference is what sits next to it. QAM Hub is a full test management system, so the day a team needs structured test cases, automated results or traceability, it is a new suite in the same project rather than a migration. The trade-off is honest too: a team that will only ever run checklists gets more product than it needs, and the interface has more in it than a single-purpose tool.

Checklist or test case?

Use a checklist whenUse test cases when
The check is one sentence and the tester knows how to do itThe steps and the expected result have to be written down
The same list is run across browsers, devices or buildsOne case is run once per run and linked to requirements
Speed of entry matters more than detailAutomation results should link to it by number
Release sign-off, smoke, UAT, exploratory sweepsRegression suites, acceptance criteria, traceability

Both live in the same project, share its tags and its bug tracker, and appear in the same runs list. Checklists are an optional module: switch them off in Project Settings and they disappear from the interface, the API and every aggregate without anything being deleted.

Plans and pricing

Checklists are included on every plan and in the free trial; there is no checklist add-on. Pricing is per seat, and read-only viewer seats for stakeholders who only read results are free, one for each paid seat. See pricing for the plans, or read how QAM Hub compares with running testing in spreadsheets.

Frequently asked questions

What is a checklist testing tool?

A checklist testing tool lets a QA team write tests as short one-line checks instead of full test cases, run the list against one or more browsers, devices or builds, and record a pass, fail, blocked or skipped result for each check. Unlike a spreadsheet, it keeps a history of who changed each result and when, links failed checks to bugs, and reports the results alongside the rest of the team's testing.

How is a QA checklist different from a test case?

A check is a single sentence the tester already knows how to perform, such as "Login works with a Google account". A test case adds numbered steps, test data and an expected result, and is usually linked to requirements and automated tests. QAM Hub keeps both in the same project: checklist suites for smoke, cross-browser, UAT and release sign-off lists, test case suites for regression and acceptance criteria.

Can I run the same checklist across several browsers or devices?

Yes. A checklist run has one column per browser, device, environment or tester, and you can add columns while the run is open. A column can be limited to a tag, so a Safari column only asks for the checks tagged for Safari. Each column shows its own progress, and the run shows an overall pass rate.

Can I import an existing test checklist from Google Sheets or Excel?

Yes. Export the sheet as CSV with the columns Group, Check, Tags and Note, in any order, and import it into a checklist suite. Nested groups are written as "Auth > Login". Checklist suites and single runs can be exported back to CSV, and a run can be exported as a PDF for people who do not log in.

Can I create a Jira bug from a failed check?

Yes. From any failed cell you can create an issue in the connected bug tracker, Jira, GitHub, GitLab, Linear, Asana, Redmine, Trello, Azure DevOps, ClickUp, YouTrack, Shortcut or ServiceNow, with the description pre-filled from your project's bug template, or link an existing issue. The bug stays attached to that cell and run and is listed in the project's Defects report.

Is QAM Hub an alternative to Testpad for checklist-style testing?

For the checklist part of the work, yes: a fast list of checks, a grid per run, keyboard entry and bugs from a cell. QAM Hub is also a full test management system, so the same project can hold structured test cases, Playwright, Cypress and JUnit XML results, requirements traceability and AI test generation. Teams that want only checklists will find more product here than they need.

Which plans include checklists, and is there a free trial?

Checklists are part of every plan and of the free trial, with no add-on. Read-only viewer seats are free, one per paid seat, so stakeholders can read results without a paid license. Checklists can be switched off per project if a team does not use them.

Read more

Try Checklists on your own project