Now that you’ve gained some confidence with how Cucumber works, it’s worth stepping back for a few moments and doing a little studying. We’re going to look at Gherkin, the language we use for writing Cucumber features.
By the end of this chapter you’ll understand how to write specifications for your software that can be both read by your stakeholders and tested by Cucumber. You’ll learn what each of the Gherkin keywords does and how they all fit together to make readable, executable Cucumber specifications. You won’t know how to run the tests yet, but you’ll be ready to write them.