About this tool
Acceptance criteria describe what should happen; testers also need what happens when things go wrong. This tool reads "As a … I want … so that …" and one acceptance criterion per line, then applies fixed rules to each criterion: every criterion gets a happy path; words such as "email", "only", "required", "upload" or "expires" add matching negative scenarios; numeric limits like "at least 12 characters" or "within 30 days" add boundary scenarios at and just past the limit. Criteria already written as Given/When/Then are reused as they are. The output is a starting point to review, not a finished test design: it cannot know your domain, so delete what does not apply and add what only you know.
How to use it
- Paste the user story. The role and goal are used in the Given and When steps.
- Paste the acceptance criteria, one per line. Prefixes like "AC1:" and bullets are removed.
- Choose which scenario types to include (alternate, negative, edge).
- Export Gherkin as a .feature file, a Markdown checklist, or CSV for a spreadsheet.
Test Scenario Generator FAQ
Is the Gherkin ready to automate?
It is syntactically valid Gherkin with tags per scenario type and criterion, but the step wording is generic. Before binding steps to code, rewrite them in your team’s domain language and merge duplicate steps so step definitions can be reused.
How are boundary scenarios found?
The tool looks for a number next to a quantifier or unit, such as "at least 12 characters", "up to 5 files" or "less than 10 MB". It creates scenarios at the limit and one step past it, and treats "less than" and "under" as exclusive limits.
What is the difference between a test scenario and a test case?
A scenario is one situation to verify ("reset link used after it expires"). A test case adds the exact preconditions, data, steps and expected result needed to execute it. Use the Test Case Generator to expand scenarios into cases.