If you feel a bit lost after looking at all this code and following along without having a full understanding of what exactly is going on, here you will find a detailed breakdown of everything that we did.
Let's start with a quick overview of what Step Definitions are. As the Cucumber framework uses the Gherkin feature document files in order to describe the business rules that are to be tested, which are represented in the form of English-like sentence statements, these need to be translated into executable code. This is the job of the Step Definition classes. Every step in a defined feature scenario needs to be matched to a method in a Step Definition class that will execute it. This matching is done by declaring a regular ...
