Test Case Generator

Runs in browser Test Design

Describe the feature, list its inputs and rules, and get a systematic set of positive, negative and boundary test cases using proven test-design techniques, exportable as table, Markdown, CSV or JSON.

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

How to use Test Case Generator

  1. Name the feature and optionally describe what it does and who uses it.
  2. List the fields one per line, e.g. "email: email, required, max=254" or "age: integer, min=18, max=120".
  3. Tick the categories you want and choose an export format.
  4. Click Generate, review the table and copy or download the export.

Test Case Generator features

  • Combines equivalence partitioning, boundary value analysis, a negative matrix and security payloads into one numbered set
  • Flow-level cases (main path, permissions, session expiry, mobile) derived from the feature description
  • Field mini-language: name: type, constraints — types and limits are inferred from names when omitted
  • Toggle positive, negative, boundary, edge and security categories independently
  • Standard columns: ID, Title, Type, Priority, Preconditions, Test Data, Steps, Expected Result
  • Export as Markdown table, JSON, CSV or Gherkin feature file with a category summary

Test Case Generator example

Registration form with two fields

Input:

Feature: Sign-up
Fields:
email: email, required, max=254
age: integer, min=18, max=120

Output:

TC-001  Submit Sign-up with typical valid values for all fields   Critical  positive
TC-007  Email: reject empty value                                   High      negative
TC-018  Age: reject below minimum (18)                              High      negative
TC-031  Age: minimum (min) = 18                                     High      boundary
TC-036  Email: html / script injection                              High      security
… 60 cases, exported as Markdown

Frequently asked questions about Test Case Generator

Which techniques does the generator apply?

Equivalence partitioning, boundary value analysis, a per-type negative matrix, security payloads and flow-level cases derived from the description (main path, permissions, session expiry). Enable Edge to add the Unicode, whitespace, date and overflow knowledge base.

How do I describe my fields?

One field per line: name: type, constraints. Types include string, email, number, integer, date, boolean, enum(a,b), url, phone, file, list and password; constraints are required, min=, max=, pattern= and unique. Names alone are enough — the type is inferred from words like email, date or price.

Can I export to my test management tool?

Yes. Choose CSV for TestRail, Xray, Zephyr or spreadsheets, JSON for scripts, Markdown for wikis and pull requests, or Gherkin to seed Cucumber, SpecFlow or Behave feature files.

Does this use AI?

No. Generation is deterministic and runs entirely in your browser, so the same input always produces the same cases and nothing is uploaded.

Why are there so many cases?

Systematic design deliberately over-generates. Untick categories you do not need, or start from the negative and boundary cases only, then prune by priority.

Technical notes

Every field is classified (numeric, length-bound, date, enum, boolean, file, list, identifier) and passed through the technique library: equivalence classes produce one positive case per valid class, the negative matrix enumerates type-specific failure modes with an expected error message, and 3-value BVA produces min−1, min, min+1, nominal, max−1, max, max+1.

The description is parsed like a user story (verb and entity detection) to add flow-level cases; ids are re-numbered sequentially after merging so exports stay stable across runs.