Paste a feature description. QA Assist drafts a structured set of functional, negative, edge, UI and performance test cases — complete with steps, preconditions, expected results and priorities. Import from Jira, review and edit cases, check coverage, organize by project, then export.
Start from a pasted spec or a Jira issue, generate structured coverage, then review the plan like a real QA artifact.
Paste a feature description or import a Jira issue with a one-time API token. The imported ticket fills the spec field.
Choose which test types you care about — functional, negative, edge, UI, performance — and how many cases to generate.
Edit cases, approve or reject them, regenerate weak cases, and save the reviewed plan to project history.
Copy or download the reviewed plan as Markdown, CSV, or Gherkin after checking the requirement coverage matrix.
QA Assist is a force multiplier — not a replacement. The goal isn't to remove testers from the loop. It's to give them a better starting point so they spend their time on what actually requires judgment.
A generated test case is a proposal, not a verdict. Every case needs a human to confirm it maps to real intent, flag assumptions the AI baked in, drop duplicates, and decide which ones graduate into your automation suite. The tests that ship are still yours — QA Assist just gets you to the review stage an hour earlier.
Spec-to-draft in seconds instead of an afternoon. Reclaim the time you were spending on the blank-page problem.
The coverage matrix maps requirements to linked cases and flags missing or partial coverage before the plan leaves the app.
Reviewed plans are saved in project history, so specs, edits, approvals and exports stay together.
Functional, negative, edge, UI/UX, and performance. Pick any combination.
P0–P3 applied consistently. No more arguing about severity in review.
ID, title, preconditions, imperative steps, single observable expected result.
Edit titles, types, priorities, preconditions, steps and expected results, then approve or reject each case.
Extract requirements from the feature text, link cases to them, and generate missing cases for gaps.
Signed-in users can import a Jira issue into the feature description without storing Jira API tokens.
Organize saved generations by project, filter history, and keep reviewed plans grouped by product area or client.
Markdown for docs, CSV for spreadsheets and TCMSes, and Gherkin for behavior-style test planning.
Signed-in runs save reviewed cases and statuses. Revisit edited plans without redoing the review.
Anthropic's Claude Sonnet 4.6 with a purpose-built QA prompt and strict structured output.
Yes. Each generated case can be edited, approved, rejected, copied, or regenerated. Signed-in users keep that reviewed state in history.
Yes. Signed-in users can paste a Jira issue URL plus a Jira email and API token to import the issue summary and description. The token is used for that request only and is not stored.
Signed-in users get a default Personal project and can create more projects from the app. New generations are saved to the selected project, and history can be filtered by project.
Reviewed plans can be copied or downloaded as Markdown, CSV, or Gherkin. The exported content reflects your latest edits and review decisions.
Yes. The coverage matrix extracts requirement-like statements from the spec, links matching test cases, and marks each requirement as covered, partial, or missing.
No. They're a drafting aid. Always have a human review the plan before it enters your suite. QA Assist helps you get to the review stage faster.
Specs are sent to Anthropic's API for generation, and signed-in generations are saved so history and projects work. QA Assist does not train AI models on your specs. Avoid pasting secrets, private keys, or regulated personal data.
5,000 characters for guests, 50,000 after signing in. That's enough for a long PRD or a detailed Jira epic. For anything larger, split it into logical sections.
Paste a spec or import a Jira issue, get a reviewable test plan, close coverage gaps, save it under a project, and export the format your team needs.