14.5. Gherkin Language for Acceptance Criteria

Gherkin is a structured language used in Behavior-Driven Development (BDD) to write acceptance tests in a readable Given–When–Then format.

Gherkin language simplifies the process of writing tests by providing a clear structure that anyone can understand, regardless of their technical background. It uses the Given-When-Then format to outline conditions (Given), actions (When), and outcomes (Then). This approach helps ensure that both stakeholders and developers have a shared understanding of what is being built and how it should behave.

Think of Gherkin like a recipe. The 'Given' part tells you what ingredients you have (the initial conditions), the 'When' part explains what steps to take (the actions), and the 'Then' part describes what the final dish should look like (the expected outcome). Just as a recipe makes cooking easier for everyone, Gherkin makes understanding requirements easier for teams.

🧩 Gherkin Syntax: K Purpose key word Gi Precondition or setup e n W Action or event h e n T Expected outcome h e n A Additional steps in sequence

The Gherkin syntax consists of several keywords that help structure acceptance criteria. Each keyword serves a specific function: 'Given' sets up the initial context or state, 'When' describes the action taken, 'Then' states the expected result after performing the action, and 'And' is used to add more steps in the sequence. Understanding these keywords is essential for writing clear and effective acceptance tests.

Imagine telling a friend about your day in a structured way: 'Given I woke up early, When I made breakfast, Then I felt energized.' Each part builds on the previous one to paint a complete picture of your story, similar to how Gherkin structures test scenarios.

🔍 Gherkin Example (Password Reset) Feature: Password Reset Scenario: Successful password reset request Given the user is on the login page And the user clicks on "Forgot Password" When the user submits their registered email address Then a reset link should be sent to that email And the link should expire in 24 hours

This example outlines a feature for resetting a password with a clear, structured approach. The 'Feature' line states what is being tested—password resets. The 'Scenario' gives a specific situation to test for success. The 'Given' lines set the stage, explaining where the user needs to be (login page) and what actions they take (clicking forgot password). The 'When' part describes the user's action of submitting their email, and 'Then' describes what should happen as a result: receiving a reset link that expires within 24 hours.

Think of this example like a script for a play. The 'Feature' sets the scene, and each line of the script (Given, When, Then) corresponds to what the actors need to do and when. In our case, the actors are the user and the system responding to the user's actions in a specified sequence.

--