Cucumber features are hard to write, and constantly break when the UI changes. But what if the fault lies not with the tool, but with the way we use it?
After years of making awful messes with Cucumber, I finally found a style that worked well, and a project I couldn't have done without it. I'd like to help you discover a way to use Cucumber that can be elegant, powerful, expressive, more accessible to your stakeholders, and resilient to even the most drastic of UI changes.
PS: Cucumber haters are welcome! Just don't heckle too much and we'll be fine. Learning Outcomes:
- You'll learn from, and hopefully laugh at, my abominations^W mistakes.
- You'll find Cucumber's sweet spot of abstraction: not super nitpicky, but not too hand-wavy either.
- You'll take away a short question you can use as a quick "gut check" to stay in that sweet spot.
- You may even be inspired to try an advanced technique that may, at first, sound a little bit wacky.
- And if you've sworn off Cucumber, you *might* just be prompted to give it another look.