Gherkinizer Logo

Gherkinizer User Guide

Convert your natural language requirements into high-quality BDD Gherkin syntax effortlessly

What is Gherkinizer?

Gherkinizer is an intelligent tool that converts your natural language requirements into high-quality BDD (Behavior-Driven Development) Gherkin syntax. Simply describe what you want to test in plain English, and Gherkinizer generates professional, behavior-focused scenarios that follow industry best practices.

Getting Started

1

Describe Your Feature

In the Natural Language Input box, describe the feature or behavior you want to test in plain English.

2

Choose Your Options

Enable Background for shared setup steps or Scenario Outline for data variations.

3

Generate & Review

Click Generate Gherkin to create your feature file and download when satisfied.

4

Generate Edge Cases

After reviewing your feature file, click Suggest Edge Cases to automatically generate additional edge-case scenarios and failure paths.

5

Save Feature File

Click Save to store the Feature in your Saved Test Cases. Free users can keep 3 files; Pro users up to 30.

6

Generate Step Bindings

Choose your preferred language and generate ready-to-use step definition skeletons.

Suggest Edge Cases

Gherkinizer can analyze your generated feature file and propose additional edge cases and failure scenarios. Simply click the Suggest Edge Cases button to see AI-powered recommendations. Review the suggestions and choose Accept & Append to merge them into your feature file or Discard to ignore them.

Note: Edge case & Failure scenario generation counts towards your generation limit.

Save Feature Files

Signed-in users can save their generated .feature files to revisit later. Click Save Feature and then open your Dashboard to view or download saved files.

Free tier: up to 3 saved files • Pro tier: up to 30 saved files.

Generate Step Bindings

Accelerate automation by generating language-specific step definition templates. After you're happy with your feature file, pick a language and click Generate Step Definitions to receive copy-ready binding code (Java available on Free tier; JavaScript, Python, C#, and Ruby on Pro).

Note: Step binding generation counts towards your generation limit.

How to Write Effective Input

Gherkinizer transforms your requirements into behavior-driven scenarios, not step-by-step test procedures.

Understanding the Generated Output

Feature Structure

  • Clear titles that describe business capability
  • Business value descriptions using "As a... I want... So that..." format
  • Focused scenarios that each test one specific behavior

Scenario Quality

  • One scenario = one behavior
  • Business language for stakeholders
  • Proper Given-When-Then structure
  • Consistent present tense throughout

Example Transformation

Your Input

"Users from different regions can sign in and should be redirected to their region-specific homepage based on their location."

Generated Output
Feature: User Authentication and Regional Access
As a platform user
I want to sign in to the platform and access region-specific content
So that I efficiently access relevant services based on my region

Background:
Given a user has valid login credentials
And the user has accepted the latest terms and conditions

Scenario: A UK user is redirected to their regional homepage
Given the user's registered region is United Kingdom
When the user successfully signs in
Then the user is redirected to the UK homepage
And the page content is localized for the UK region

Best Practices for Input

1. Use Natural Language

Write as if explaining to a colleague:

  • "Users should be able to..."
  • "When a customer does X, they should see Y"
  • "The system should prevent users from..."

2. Include Edge Cases

Mention important variations:

  • "Users with expired accounts should see a renewal message"
  • "Invalid email formats should show an error"

3. Specify User Types

Be clear about who is acting:

  • "Registered users can..."
  • "Guest visitors should..."
  • "Administrators have the ability to..."

4. Mention Expected Outcomes

Always include what should happen:

  • "...and should see a success message"
  • "...and be redirected to the dashboard"

Common Scenarios Gherkinizer Handles Well

Authentication & Authorization

  • User login/logout flows
  • Password reset procedures
  • Role-based access control

E-commerce & Shopping

  • Product browsing and searching
  • Shopping cart management
  • Checkout processes

Form Handling

  • Data validation
  • Error messaging
  • Successful submissions

Navigation & UX

  • Page redirections
  • Menu functionality
  • Search capabilities

When to Use Background vs Scenario Outline

Use Background When:

  • Multiple scenarios share the same setup steps
  • All scenarios need the same initial conditions
  • You want to avoid repeating common Given steps

Use Scenario Outline When:

  • Testing the same behavior with different data
  • Validating various input combinations
  • Covering different user types for the same action

Tips for Better Results

Be Descriptive

✗ "Test the login"

✓ "Verify that registered users can log in with their email and password and access their personal dashboard"

Include Context

✗ "User clicks button"

✓ "When a user with items in their cart clicks the checkout button, they should be taken to the payment page"

Mention Variations

✗ "Test password validation"

✓ "Users should see specific error messages for passwords that are too short, missing special characters, or commonly used"

Getting the Most from Gherkinizer

  • 1
    Start Simple: Begin with straightforward scenarios before tackling complex workflows
  • 2
    Think Like a User: Focus on what users want to accomplish, not system internals
  • 3
    Be Specific: Detailed descriptions lead to better Gherkin output
  • 4
    Review and Refine: Use generated scenarios as a starting point and refine as needed
  • 5
    Collaborate: Share generated scenarios with your team to ensure they capture the intended behavior

Need Help?

If your generated Gherkin doesn't match your expectations, try rephrasing your input to be more specific, break complex workflows into separate behaviors, or focus on the user's perspective and desired outcomes.

Gherkinizer is designed to help you create professional, maintainable BDD scenarios that serve as living documentation for your applications.