Chapter 6When Cucumbers Go Bad
When your team first starts to use Cucumber, it won’t be long before you start to notice that you seem to be creating code with fewer bugs than you did before. You might find yourself bravely refactoring code that previously you would have been too scared to touch. You’ll continue adding feature after feature, inspired by the delight you felt on seeing your first passing scenario.
After a while, however, things can start to turn sour. Suddenly it dawns on you that the tests take a really long time to run. Or perhaps you’ve started to notice a couple of scenarios that seem to fail at random, usually just when you’re up against a tight deadline. Perhaps the nontechnical stakeholders have lost interest in the process, ...
Get The Cucumber Book now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
