About this tool
Most features fail in the same well-known ways: login forms that reveal which accounts exist, uploads that trust a file extension, checkouts that charge twice on a double-click, APIs that let one user fetch another user’s records. This generator starts from fixed templates of those cases, so you do not have to remember them every time. Pick a template, choose whether to include negative, boundary, security and accessibility cases, and you get a table with IDs, preconditions, steps, test data, expected results, priority and type. Every cell is editable, and you can add or delete rows. The templates use example limits (5 failed attempts, a 10 MB upload, 8-character passwords) that you should replace with the values in your specification. The cases come from templates written by people, not from an AI model.
How to use it
- Enter the feature name and choose a template. For form field validation, also choose the field type.
- Set the ID prefix (for example TC-LOGIN gives TC-LOGIN-001) and tick the case types to include.
- Click Generate test cases, then edit cells, delete rows that do not apply and add your own.
- Export as CSV (one row per case or one row per step), Markdown or tab-separated values for Excel.
Test Case Generator FAQ
How do I import the CSV into TestRail?
Use the "CSV (one row per case)" export and TestRail’s CSV import for test cases. In the column mapping step, map Title to Title, Preconditions to Preconditions, Steps to Steps and Expected Result to Expected Result (text template), and Priority and Type to their fields, mapping values where your TestRail names differ. ID can be ignored or mapped to a custom field.
How do I import into Xray or Zephyr Scale?
Use "CSV (row per step)". Each step is a row with Test ID repeated, so the importer can group steps into one test. In Xray’s Test Case Importer map Test ID to the test identifier, Title to Summary, Action, Test Data and Expected Result to the step fields. In Zephyr Scale’s CSV import map Title to Name, Preconditions to Precondition, and Action/Test Data/Expected Result to the step-by-step script columns.
Will regenerating overwrite my edits?
Yes, regenerating replaces the table, so the tool asks first. Your edited table is saved in this browser between visits until you reset it.
Why are some limits like "5 attempts" or "10 MB" in the cases?
Concrete values make a case executable. They are examples. Replace them with the numbers from your requirements before running the tests.