Skip to content

Feature · Development · Test suites

Order out of
chaos.

Projects hold suites, suites hold cases, and every case moves through a deliberate approval workflow. Try it — click the statuses.

16 case typesinline editingimport .csv / .xlsx / .json
qamind — suites / auth · password resetAPPROVAL FLOW

Click a status — Draft → Ready → Approved

TC-041Valid reset — password updated
TC-042Link expires at 30-min boundary
TC-043Reused token rejected
TC-044Unknown email — generic response
1/4 approved

The real approval flow — only Approved cases can become automation scripts.

In the product

How it actually works.

1

Structure by project and suite

Group cases by feature, module or sprint. Suites expand inline; names edit in place; counts and approval stats live on the card.

2

Edit everything in the side panel

The case panel covers all of it — steps, expected results, priority, one of 16 case types, assignee, requirement ID, prerequisites, tags.

3

Approve like you mean it

Draft → Ready → Approved is a gate, not decoration: script generation and runs only consume approved cases, so nothing half-reviewed becomes automation.

qamind — feature walkthroughVIDEO

See these steps on screen

coming soon

A guided video of this exact flow is being recorded — it will live right here.

Spec sheet

The fine grain.

Case fieldsTitle, steps, expected result, priority, type, status, assignee, requirement ID, prerequisites, tags
Case types16 — Functional, Integration, E2E, Boundary, Negative, Exploratory, Accessibility and more
WorkflowDraft → Ready → Approved, with bulk status changes
ImportCSV, XLSX and JSON — bring your legacy cases along
Cost0 tokens — organising and editing are always free

Give every case a home and a verdict.