14.4. Acceptance Criteria

Acceptance criteria define boundaries and conditions that the user story must meet to be accepted as done. They ensure clarity, testability, and shared understanding between stakeholders and the development team.

Acceptance criteria are specific conditions that a user story must satisfy for it to be considered complete. They help clarify the expectations of all parties involved — including the development team and stakeholders — ensuring that everyone has the same understanding of what 'done' means. By defining these criteria, teams can avoid misunderstandings that might arise from ambiguous user stories.

Imagine you're planning a birthday party for a friend. You might set criteria for the party to be deemed successful: there should be a cake, at least five guests, and a playlist of their favorite songs. If these conditions are met, you can confidently say the party was a success. Similarly, acceptance criteria help teams know when they have successfully met a user's needs.

✅ A reset password link is sent to the registered email. ✅ The link expires after 24 hours. ✅ The user is prompted to enter a new password upon clicking the link.

These examples illustrate specific acceptance criteria related to a password reset feature. Each of these points clearly states what needs to happen for the story to be considered complete. For instance, the first criterion ensures that a user receives a password reset link, which is essential for fulfilling the user's request. The second specifies a time limit for the link's validity, adding a layer of security. The third states that the user must be prompted to create a new password, which is the final step needed to complete the process.

Think of these acceptance criteria like a recipe for baking a cake. First, you need the right ingredients (the reset link), then you need to bake it for a specific amount of time (the expiration period), and finally, you need to decorate it before serving (prompting for a new password). Each step must be completed for the cake to be perfect!

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

Gherkin language is a tool that helps in writing acceptance tests in an easily understandable format. It follows a structure that includes three key components: 'Given' describes the initial context or setup, 'When' indicates the action that the user takes, and 'Then' outlines the expected outcome. This structured approach not only makes tests more readable but also aids in collaboration between technical and non-technical team members.

Consider teaching someone to drive using Gherkin language. You can set the context: 'Given the car is parked on the street', then describe the action: 'When the driver starts the engine', and finally state the expected result: 'Then the car is ready to drive'. This clear format helps anyone understand the steps involved.

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 chunk provides a practical example of how acceptance criteria for the password reset feature could be written using Gherkin syntax. The feature is the general functionality being described (Password Reset), while the scenario outlines a specific case — a successful password reset request. The steps clarify what needs to happen from the user's perspective (the given state, the action taken, and the resulting state). This format allows developers to visualize the user interaction and understand what needs to be tested.

Using the earlier cake analogy, think of this Gherkin syntax as a detailed instruction manual for baking the cake. It tells you the starting point (you have a baking pan), what to do next (mix ingredients), and the end goal (the cake is ready to be served). Each step is clear and ensures you’re on the right track.

--