Templates
Paste requirements, generate test cases, and review CSV or Gherkin examples from one QA workflow.
Working from Jira requirements? Use the AI test case generator for Jira to export CSV, Xray, and Zephyr-ready cases.
Fast workflow
Start with a PRD excerpt, user story, Jira issue, or acceptance criteria. The generator drafts manual cases, CSV fields, Gherkin scenarios, negative tests, edge cases, and missing criteria notes.
QA knowledge base
Requirements to test case generation maps product rules, user flows, constraints, and acceptance criteria into practical QA coverage that can be reviewed before release.
Use clear requirements, acceptance criteria, validation rules, user roles, constraints, and examples of valid or invalid data.
| ID | Title | Priority | Type | Expected Result |
|---|---|---|---|---|
| REQ-001 | Verify the requirement's main success path | High | Positive | The feature behavior matches the stated requirement and acceptance criteria. |
| TC-002 | Verify weak password is rejected during reset | High | Negative | The form blocks submission and explains the password rule that failed. |
| TC-003 | Verify expired reset link cannot be used | Medium | Edge Case | The link is rejected and the user can request a fresh reset email. |
Paste the requirement, add acceptance criteria, roles, business rules, constraints, and sample data, then generate positive, negative, boundary, and error-handling test cases. Review traceability before exporting CSV, Gherkin, or Jira-ready rows.
Yes. The generated missing-criteria checklist can highlight unclear password rules, time windows, permission states, error behavior, and data constraints.
Paste the requirement, add acceptance criteria or assumptions, choose the output format, then review the generated positive, negative, edge, CSV, and Gherkin coverage before using it in your QA workflow.
Yes. Choose Both to review manual test cases, CSV-style fields, and Given/When/Then scenarios from the same product requirement.
Use the acceptance criteria generator first when the requirement is vague. Better criteria usually produce clearer test cases and fewer assumptions.
Yes. The generator can structure cases as a CSV-ready table with title, preconditions, steps, expected result, priority, type, and test data fields.
No. It accelerates first-draft coverage, but QA teams should review edge cases, business rules, and product-specific risks before importing cases.
A clear user story, acceptance criteria, business rules, constraints, and examples of valid or invalid test data produce the strongest output.
To create test cases from requirements, provide structured requirement text, acceptance criteria, user roles, business rules, constraints, and test data examples. Generate positive, negative, boundary, and error-handling cases, then review the result before exporting CSV, Gherkin, or Jira-ready fields.
Include the requirement, user role, goal, business rules, dependencies, permissions, validation rules, limits, and examples of valid and invalid data. The more structured the input, the easier it is to trace each generated test case back to a requirement.
Use AI output as a draft. QA should verify traceability, remove duplicates, confirm expected results, add product-specific risks, and send unclear assumptions back to product before importing cases into a test management tool.
Coverage matrix
| Coverage type | What to test | Example |
|---|---|---|
| Positive | Happy-path behavior for valid users, valid data, and expected system state. | Customer applies a valid promo code and the order summary shows the discount. |
| Negative | Rejected actions, invalid inputs, missing required fields, and permission failures. | Customer applies an expired promo code and receives a clear validation message. |
| Boundary | Minimum, maximum, zero, expiry, rate limit, and near-threshold behavior. | Discount cannot reduce the order total below zero. |
| Error handling | Recoverable failures, unavailable dependencies, retries, and safe messaging. | Payment provider returns an error and the cart remains intact for retry. |
Output examples
TC-001, Verify promo code applies to eligible order, High, Positive, Preconditions: guest checkout with eligible cart, Expected: discount appears in order summary.
Given a guest shopper has an eligible cart, when they apply a valid promo code, then the order summary shows the discount and updated total.
Summary: Verify expired promo code is rejected. Priority: High. Component: Checkout. Labels: qa, promo-code. Expected Result: validation message is shown and checkout can continue.
Confirm every business rule, permission state, validation error, limit, and recovery path has at least one test case.
Related tool
If the requirement is still vague, use the acceptance criteria generator first. Clear Given/When/Then criteria make the requirements-to-test-cases output more precise and easier to review.
Read more
Generate manual QA test cases, software test cases, requirements-based cases, and user-story test cases with examples and templates.
QA templates - 6 min readUse the acceptance criteria generator to turn feature notes into testable rules, QA checks, and Given/When/Then examples before sprint handoff.
Acceptance criteria - 5 min readSee how a password reset story becomes reviewable QA cases with priorities, types, and expected results.
Guide - 6 min read
Turn acceptance criteria into Given / When / Then scenarios for product and engineering review.
BDD - 5 min read
Convert Jira stories into manual test cases, Gherkin, CSV, Xray, and Zephyr-ready QA rows for sprint review and import.
Jira QA - 5 min readPaste a Jira story, bug report, or acceptance criteria and export Classic cases, Gherkin, CSV, Excel, Xray, or Zephyr-ready fields.
Jira workflow - 5 min read
Use the review console to inspect steps, preconditions, expected results, and suggested test data.
QA workflow - 7 min readDraft Playwright MCP test steps, automation cases, and Claude Code prompts from a URL and acceptance criteria.
Playwright MCP - 6 min readGenerate smoke checks, tool-call cases, malicious input probes, permission checks, and Claude Code or Cursor prompts for MCP server testing.
MCP testing - 7 min readUse a replay checklist, immutable audit log fields, trace template, and comparison table to reproduce failed AI agent interactions.
Agent QA - 6 min readFormat generated QA cases for CSV review, Excel handoff, and Jira-connected imports.
Export workflow - 4 min read