CoverageHeatmap of tested vs untested areas — spot gaps instantly
WalkthroughVisual step-by-step simulator — run tests without code
▶
3 ways to run tests — pick your comfort level
🎬Walkthrough tab — zero setupbeginner
Click "Run all tests" — QAGen simulates each step visually, raises bugs on failures. No installation needed.
⚡Local proxy — real browserintermediate
Run node proxy.js once. Playwright opens a real browser and tests your actual app. Results come back to QAGen.
🔄CI/CD — runs on every PRautomated
In BDD tab → Step 3 → Download GitHub Actions workflow. Merge it once — tests auto-run on every pull request forever.
🐛
Bug tracking is fully automatic
When a test fails — in the simulator or via proxy — QAGen auto-raises a bug report with everything pre-filled.
🐛
Bugs tab — view all raised bugs, filter by status, push to Jira/GitHub with one click
📋
Bug Report tab — formal report with bug ID, env, severity, status — export as .txt
🔄
Jira two-way sync — when you fix a bug in Jira and close the ticket, QAGen auto-updates the status here
🚀
You're set. Here's what to do first:
Keyboard shortcuts:
In the Walkthrough tab — R run all
S step
Esc reset
Session auto-saves every time you generate. Come back and it's all here.
Generate test cases in seconds, not hours.
Describe your feature, paste a URL, or upload a PRD — AI generates structured test cases, BDD scenarios, Jira tickets, coverage analytics, run history, and a live visual simulator. Completely free.
0
cases generated
0
high priority
0
test types
~0m
time saved
0
runs executed
0
bugs raised
Try a sample:
Feature description
0 / 3000
Feature / product URL
⚠️
URL fetching not supported in browser
This app can't fetch external URLs directly (browser security restriction). Instead, open the URL, copy the page content or requirements, and paste it below.
Paste page content / requirements here
0 / 3000
Upload PRD / spec
📎
Drop your PRD, spec, or feature doc here
PDF, TXT, MD, DOCX · max 10MB
📄
// optional extra context
User story (Gherkin / plain)
0 / 3000
Generation options
What should AI generate?
Choose the format your team uses for writing and running tests.
📋 Test CasesStep-by-step test cases with expected results — for manual QA testers
🥒 BDD / GherkinGiven / When / Then format — ready for Cucumber, Cypress, Playwright
⚡ Both formatsGet test cases AND Gherkin scenarios together
Which priority levels to generate?
Focus the AI on what matters most, or get full coverage.
🎯 All prioritiesHigh + Medium + Low — full test coverage across all scenarios
🔴 High priority onlyOnly critical paths that must not break before release
Output language
Test case names, steps, and expected results will be generated in the selected language
Analyzing feature specification...
✓ Session restored — your last QA session was saved automatically.
What to do next — based on your role
QA Output
Push to your tools
Send bugs, test cases, and reports directly — no copy-paste
🎯
Jira
Push bugs as tickets
not set up
🐙
GitHub
Commit tests · create issues
not set up
📝
Notion
Write QA report page
not set up
💬
Slack
Notify team of QA results
not set up
Set up tokens in Vercel env vars: ATLASSIAN_TOKEN · GITHUB_TOKEN · NOTION_TOKEN · SLACK_BOT_TOKEN
📊
Coverage score, stats, and key metrics will appear here after generating.
0
total cases
0
high priority
0
medium priority
0
low priority
0%
coverage score
requirements · types · priority
Feature summary
Coverage areas
🔗
Requirements matrix appears after generating. Shows which requirements have test coverage.
Each requirement is linked to the test cases that cover it. Use this to ensure full coverage before shipping.
📋
Test cases appear here after generating. Filter by priority, search, and edit inline.
0 selected
🥒
BDD / Gherkin scenarios and runnable test code appear here after generating.
Step 1 — Gherkin Scenarios
AI-generated from your PRD. Used as the spec for code generation below.
Step 2 — Generate Test File
One complete, runnable test file covering your entire feature — all scenarios in a single describe() block.
Choose framework:
feature.cy.js
Analyzing all scenarios...
Step 3 — Run Tests Without Manual Effort
Pick how you want tests executed — all options run the real generated code
⚡
Run now via proxy
fastest · results in QAGen
Start the local proxy once. QAGen sends the generated code directly to Playwright — real browser, real results, zero copy-paste.
Proxy not running?
# one-time setup
npm install && npx playwright install chromium
# start proxy
node proxy.js
🔄
Auto-run on every PR
one-time setup · runs forever
Generate a GitHub Actions workflow. Merge it once — tests run automatically on every pull request, no human needed.
💻
Copy terminal command
paste once · works anywhere
One command that downloads the test file and runs it immediately — no manual file management.
Generate test file first ↑
Real execution results
Darker = better coverage. Use gaps to prioritise where more testing is needed.
Coverage:
NoneLow (1)Medium (2-3)Good (4+)
Format:
📋
No runs yet. Execute tests in the Walkthrough tab.
Pass rate trend
📌
Save versions of your test suite here. Click "Save version" after generating.
Version History
Save named snapshots of your test suite and compare what changed across PRD revisions.
☁
Cloud Test Runner
Run Playwright in the cloud — no local proxy needed. Free to self-host on Railway or Render.
🧩
VS Code Extension
Generate tests from inside VS Code — right-click any PRD file or selection
# Install from VSIX
cd qagen-vscode && npm install && npm run package
code --install-extension qagen-vscode-1.0.0.vsix
Then: right-click any .md/.txt file → QAGen: Generate tests from this file
🔄
Jira Two-Way Sync
When a Jira ticket resolves, QAGen auto-updates the bug status