Requirements → Test Cases

Runs in browser Test Design

Paste requirements (one per line or numbered) to generate one or more test cases each, with IDs and a traceability matrix you can export.

Privacy: This tool runs entirely in your browser. Your input never leaves your device.

How are test cases derived from a user story?

A user story ("as a customer I can pay with a saved card so that checkout is faster") becomes testable through its acceptance criteria: each criterion, written as a precondition, an action and an observable result, maps to at least one test case, and the questions the story does not answer — a declined card, an expired one, no saved card at all — become the negative cases. The story's benefit clause ("so that") says what to measure; the role says which permissions to test with. A story with no acceptance criteria is not ready for testing, and usually not for development either.

Read the guide: How to Write Test Cases

How to use Requirements → Test Cases

  1. Paste the requirements, one per line.
  2. Generate to see the traceability matrix and the cases.
  3. 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, plus a boundary case when a validation requirement mentions numbers
  • 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        functional  High      TC-003, TC-004   2

Frequently 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. A validation requirement that mentions numbers also gets a boundary-values case.

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.

References