Skip to content

Feature · Execution · Run history

Terminals forget.
Ledgers do not.

Every run is kept — per-case pass, fail or skip with duration and full error output. Click into the ledger.

per-case resultsfull error outputsearchable history
qamind — execute tests / run ledgerHISTORY

Click a run — every result is kept

TC-041Valid reset — password updated1.9s
TC-042Link expires at 30-min boundary3.4s

✗ expected “link expired” — got form at 00:31:07

TC-043Reused token rejected1.2s
TC-041Valid reset — password updated2.0s
TC-042Link expires at 30-min boundary3.1s
TC-043Reused token rejected1.3s
TC-107Quantity change recalculates totals2.6s
TC-108Declined card — cart preserved4.1s
TC-110Confirmation email sent

The run ledger — expand any run for its per-case results and error output.

In the product

How it actually works.

1

Scope the run

All approved cases, selected suites, or hand-picked cases — the configurator makes the run match the question you are asking.

2

Execute on your machine

The local Playwright runner is a small Node process on localhost; scripts run in your environment and stream results back.

3

Read the results forever

Status header, segment meter, expandable per-case results with logs and errors — filterable by status and date, searchable by label, paginated.

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.

Per-case datapass / fail / skip · duration · logs · full error output
FiltersStatus (all/passed/failed/running), date range, label search
On failureOne-click Record as Bug with the evidence attached
HistoryPaginated ledger — 10 runs per page, kept indefinitely
CostViewing history is free; runs deduct tokens

Keep the receipts for every run.