From the course: Behavior-Driven Development

Unlock the full course today

Join today to access over 22,700 courses taught by industry experts or purchase this course individually.

Translate the scenario into Gherkin

Translate the scenario into Gherkin - Cucumber Tutorial

From the course: Behavior-Driven Development

Start my 1-month free trial

Translate the scenario into Gherkin

- Now that we have a general understanding of what Gherkin is, let's revisit the three amigos conversation from before. In that conversation, we discussed our scenario with concrete examples, identified an edge case, and attempted to resolve misunderstandings as early as possible. This process assisted us in creating clear acceptance criteria for our scenarios. Remember our user story from before, the customer pays with a credit card. As a sales associate, I should be able to process payments when given a credit card. Now we're ready to translate our conversation into scenarios that describe the concrete behavior of the application. Ideally, this is done using declared dephrasing, meaning without referencing the particulars of a user interface or sequence of steps. Remember that Gherkin is a way to phrase our acceptance criteria as an executable scenario that describes the behavior of a system. So, our conversations would describe the behavior of the system under specific initial…

Contents