How to use Requirements → Test Cases
- Paste the requirements, one per line.
- Generate to see the traceability matrix and the cases.
- Download the matrix as CSV for your RTM and the cases in the format you need.
Requirements → Test Cases features
- Accepts numbered lines, REQ-n / FR-nn identifiers, bullets and plain lines
- Classifies requirements (functional, validation, security, performance, UI, data, integration) and infers priority from must/shall/should/may
- At least two traceable cases per requirement, including boundaries when numbers are mentioned
- Requirement-to-test traceability matrix
- Export as Markdown, JSON (with the requirement list), CSV or Gherkin
Requirements → Test Cases example
Password reset requirements
Input:
REQ-1: The system shall allow users to reset their password via an emailed link.
REQ-2: Reset links must expire after 30 minutes.Output:
Requirement Kind Priority Test cases Count
REQ-1 security High TC-001, TC-002 2
REQ-2 validation High TC-003, TC-004, TC-005 3Frequently asked questions about Requirements → Test Cases
Which requirement formats are recognised?
Numbered lines (1., 2.), identifiers such as REQ-3, FR-01 or [SRS-12], bullet points and plain lines. Missing identifiers get sequential REQ-nn ids.
How many cases per requirement?
At least two: a positive verification and a kind-specific counterpart — invalid input for validation rules, bypass attempts for security, load measurement for performance, dependency failure for integrations, and boundaries when the text contains numbers.
What is in the traceability matrix?
One row per requirement with its kind, priority (from must/shall/should/may wording), the test case ids that cover it and the count — ready for an RTM in your test plan.
Can I export everything?
The matrix downloads as CSV; the cases export as Markdown, JSON (including the requirement list), CSV or Gherkin.