QA Test Case Generator — Requirements & Mockups
Generate traceable, non-duplicated manual QA test cases from requirements, user stories, mockups, and templates.
Free
Works with the AI Agents you already use
Claude Code
Cursor
Codex CLI
Muse
Dots+22 moreClaude CodeCursorCodex CLIMuseDots
OpenClaw
Manus
Grok
Grok Bot+18 agentsQA Test Case Generator — Requirements & Mockups
Example session with this skill installed
Use qa-test-case-generation to compare these checkout requirements with the observed mockup and generate traceable manual test cases. Requirements: REQ-CHK-01 requires email and shipping address; REQ-CHK-02 allows one valid discount code; REQ-CHK-03 requires subtotal, discount, and final total. Mockup: Email, Address, City, Country, Postal Code, Apply code, Subtotal, and Total are visible, but no Discount row is shown. Include gaps, assumptions, clarifications, negative cases, and boundary risks.
- Read your context and instructions
- Compiled the qa test case
Requirement Summary
- REQ-CHK-01 requires an email and shipping address before checkout can continue.
- REQ-CHK-02 allows one valid discount code.
- REQ-CHK-03 requires subtotal, discount, and final total in the order summary.
Requirement vs Mockup Gap Analysis
| Finding | Source | Analysis |
|---|---|---|
| Email and shipping address are represented | Requirement + Mockup | Visible fields support the required checkout data. |
| Required state of City, Country, and Postal Code is unclear | Mockup | The requirement does not define which address components are mandatory. |
| Discount row behavior is not shown | Requirement + Mockup | REQ-CHK-03 requires a discount line, but the initial mockup has no applied-code state. |
| Invalid or expired code behavior is undefined | Inferred QA Risk | No requirement defines the message or whether the entered code remains editable. |
Assumptions
- The final total equals subtotal minus the accepted discount.
- The Discount row may appear only after a valid code is applied.
Clarifications Needed
- Which shipping-address fields are required?
- What message should appear for invalid, expired, or already-used codes?
- Are discount codes case-sensitive?
Test Cases
| ID | Scenario | Steps | Expected Result | Source |
|---|---|---|---|---|
| TC-CHK-001 | Verify required email and shipping address validation | Leave Email and Address empty, then select Continue. | Visible required validation appears and checkout does not continue. | REQ-CHK-01 + Mockup |
| TC-CHK-002 | Verify one valid discount updates the summary | Enter a valid code, select Apply code, and review the summary. | The code is accepted, a Discount row appears, and final total equals subtotal minus discount. | REQ-CHK-02 + REQ-CHK-03 + Mockup |
| TC-CHK-003 | Verify an invalid discount does not change the total | Record the total, enter an invalid code, and select Apply code. | The code is not applied, an explanatory error appears, and the total remains unchanged. | Inferred QA Risk; exact message needs clarification |
| TC-CHK-004 | Verify summary values are mathematically consistent | Apply a valid discount and compare subtotal, discount, and total. | All three values are visible and the displayed total is mathematically correct. | REQ-CHK-03 |
Missing or Unclear Requirements
- Required shipping-address components
- Discount-code case sensitivity, eligibility, and error messages
- Currency and rounding rules
Suggested Improvements
- Add a mockup state showing a successfully applied discount.
- Define complete shipping-address validation rules.
Connects securely to your tools. The creator never sees your data.
About this skill
QA Test Case Generation helps an AI agent turn written requirements and optional UI references into practical manual test cases. It analyzes BRDs, user stories, acceptance criteria, tickets, supported documents or spreadsheets, screenshots, wireframes, and accessible prototype URLs. When requirements and mockups are both available, it reports missing UI elements, extra controls, label or workflow conflicts, and unclear behavior before generating cases.
What it covers
- Relevant happy paths, negative scenarios, boundaries, validations, permissions, workflows, UI behavior, regression risks, and data persistence
- Requirement-to-mockup gap analysis
- Template preservation and duplicate removal
- Source traceability for requirements, mockups, and inferred QA risks
Outputs
A requirement summary, mockup observations when applicable, gap analysis, assumptions, clarifications, coverage strategy, test case table, missing requirements, and suggested improvements.
Requirements
Provide at least one requirement source. Optional inputs include mockups, templates, existing cases, roles, permissions, and business rules. The active agent needs suitable document, spreadsheet, image, or browser tools for non-text inputs.
Privacy and dependencies
This skill is instruction-only. It has no runtime dependencies, API keys, subscriptions, paywalls, or bundled network service.
Limitations
It designs manual test cases but does not execute them or guarantee defect-free software. Coverage depends on the supplied material. UI mockups cannot prove backend behavior, authorization, integrations, performance, persistence, or accessibility conformance. Protected content requires user-authorized access or screenshots; the skill does not bypass authentication.
Free and open source under the MIT License.
How to use
Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free forever
No account required to browse
Trust & safety
Security scanned
Verified clean 15 days ago
- Free to download with an account
Requires
Python