February 2015
Intermediate to advanced
338 pages
8h 16m
English
This section builds on the techniques of the previous section to use Gherkin tags to modify the behavior of our step definitions. The advantage of using tags, rather than environment variables, is that the number of layers exercised by the test is documented in the feature file for the whole team to see.
In the previous sections we put a seam in place that allowed AtmInterfaceFactory to decide whether our step definitions were going to interact with the Teller through the web UI or its Java API. We’re going to reuse that seam in this section, but we’ll use Gherkin tags to modify the factory’s behavior, instead of the environment variable that we used previously.
The Cucumber feature ...