>_ qa::checklist_
Build a checklist by module, task, or business area, mark pass/fail/pending status, add comments for blockers, and export a clean CSV when the team needs a status update.
~/projects/Smoke test
| # | check | expected_result | status? | comment | ||
|---|---|---|---|---|---|---|
| 01 | Login accepts valid email | User lands on the dashboard | Password reset link times out | |||
| 02 | Checkout total matches cart | Tax and discount stay correct | Ready for handoff | |||
| 03 | Mobile menu closes after tap | Menu closes and route changes | Header overlaps at 390px |
built for
QA engineers
Track manual checks for any QA scope: new features, bug fixes, integrations, mobile, UAT, and audits.
built for
Founders and small teams
Track business goals as checklists: purchases, weekly tasks, monthly plans, yearly priorities, and launch work.
built for
Dev and product teams
Turn quality control status into a clear table with failures, comments, and unfinished tasks.
about
Bringing clarity and order to your workflow
Organize any scope
Create one project for a QA pass, launch plan, purchase list, weekly tasks, monthly goals, or recurring work.
$ ls ./projects
4 projects
Smoke test
API
Purchases
Monthly goals
Track what blocks progress
Mark each item as pass, fail, or pending so the team can see what is done, blocked, and still open.
Export the status
Send a CSV with groups, checks, expected results, statuses, and comments when someone needs a clear update.
$ export --csv
handoff.csv ready
faq
- Is this a heavy test management suite?
- No. qa::checklist is a lightweight checklist workspace for manual checks, statuses, comments, and CSV exports.
- When should I use it?
- Use it for QA passes, launches, hotfixes, audits, weekly tasks, monthly planning, purchases, or any checklist that needs visible status.
- What goes into the CSV export?
- Each export includes project, module, check, expected result, pass/fail/pending status, and comment fields.