The Cucumber for Java Book

Chapter 13Keeping Your Features Fast

We’ve driven out some new functionality in our CashSlot to handle errors that might arise when the ATM tries to dispense money to the customer. We also implemented functionality that lets users know if the ATM doesn’t hold enough money to satisfy their request before they even press the Submit button. The scenarios are all running through the ATM UI in a single browser session, which seems fast enough at the moment.

However, we’ll want to develop hundreds, if not thousands, more scenarios before we ship our application so the runtime of our features will continue to increase. Many of the scenarios that we write will exercise the same parts of the UI over and over again, not because it gives us any extra ...