The team decides to start with the Valet Parking examples from Table 1.11 of the parking lot story. The team chooses Cucumber1 to automate the tests. Cucumber uses Ruby to glue together the data representation of the examples and the system under test. Each set of tests in Cucumber is called a feature. A feature goes into a text file on its own.
In order to automate a test in Cucumber, we need a combination of features that holds our data, some definition of test steps to interact with the application under test, as well as a set of environmental settings.
Tony has the diagram shown in Figure 2.1 in mind for the overall architecture.
The examples ...