Acceptance Criteria Generator

Runs in browser Test Design

Template-driven Gherkin acceptance criteria covering the main flow, alternates, validation, permissions and non-functional expectations for any user story.

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

What are acceptance criteria?

Acceptance criteria are the conditions a user story must satisfy to be considered done, agreed before development starts and written so that each can be checked: "Given a registered user with an expired card, when they pay, then the order is not created and the card error is shown." Each criterion becomes at least one test, which is how testers, developers and product owners end up testing the same thing.

Read the guide: How to Write Test Cases

How to use Acceptance Criteria Generator

  1. Paste the user story ("As a … I want … so that …"), optionally with bullet-point criteria.
  2. Choose Gherkin or Markdown output.
  3. Generate, review the scenarios with the team and save the .feature file.

Acceptance Criteria Generator features

  • Gherkin feature file with narrative and tagged scenarios
  • Happy path, minimal data, validation, permissions, failure and accessibility scenarios
  • Verb-specific scenarios (duplicates, concurrent edits, declined payments, file rejections…)
  • Bullet points under the story become extra criteria scenarios
  • Definition-of-done checklist; Markdown alternative to Gherkin

Acceptance Criteria Generator example

Criteria for saving a shipping address

Input:

As a registered customer
I want to save my shipping address
So that I can check out faster next time

Output:

Feature: Save my shipping address

  @happy-path @critical
  Scenario: Registered customer can save their shipping address
    Given I am signed in as a registered customer
    And I have permission to save my shipping address
    When I save my shipping address with valid information
    Then the action succeeds
    And I see a confirmation that the shipping address was processed
    And I can check out faster next time

Frequently asked questions about Acceptance Criteria Generator

What format is generated?

A Gherkin feature file with tagged scenarios (happy path, validation, permissions, failure, accessibility and verb-specific cases) plus a definition-of-done checklist. A Markdown checklist is available as an alternative.

Do I need the exact "As a / I want / So that" wording?

It works best with that pattern, including the three-line variant, but tolerant parsing also handles "I need", "in order to" and bullet lists of extra criteria.

Can I use the output directly in Cucumber?

The .feature output is valid Gherkin. Bind the steps to step definitions in Cucumber, SpecFlow, Behave or Playwright-BDD, or keep it as living documentation.

Why are permission scenarios always included?

Authorisation gaps are among the most expensive defects. Every story gets an unauthenticated, wrong-role and other-user's-data scenario so they are discussed before development starts.

References