A browser
requiredEverything core — projects, generation, suites, bugs, analytics — runs in the web app. Nothing to install.
Field manual — How it works
QAMind covers the whole testing lifecycle, but not everyone starts it the same way. Pick your situation — the manual adapts.
The document path — best when requirements exist, even messy ones.
Name it, pick the app type, test framework and script language, set the base URL of the app under test. Sprint or Kanban — your call.
→ you get: project + auto-scaffolded sprints
PDF, Word, Excel, CSV, Markdown — even a screenshot. QAMind extracts the text and reads the requirements.
→ you get: parsed requirement text
AI drafts structured cases — title, steps, expected result, priority, requirement ID. Edit anything inline; approve what's right. Draft → Ready → Approved.
→ you get: approved cases in a suite
Approved cases become Playwright or Selenium code in TypeScript, JavaScript, Python, Java or C#. Copy, download, or save to the workspace.
→ you get: .spec.ts / .py / .java / .cs files
Execute through the local runner. Failures carry full error output, and “Record as Bug” files a linked defect in one click.
→ you get: run history + tracked defects
Watch the whole loop
coming soonAn interactive walkthrough of all five moves is in production — it will sit right here.
Requirements
Almost nothing. The heavier pieces are optional and only unlock extra paths.
Everything core — projects, generation, suites, bugs, analytics — runs in the web app. Nothing to install.
Only for the recording path. Free download; captures real sessions and imports them into your workspace.
Only for executing generated scripts on your machine — a small Node process QAMind talks to on localhost.
What costs what
AI work costs tokens. Human work never does.
Standard refills 100 tokens daily at midnight. Premium is uncapped. Full pricing →