Mike Swieton recently posted Never say “Click” advocating the use of custom steps over browser-centric ones. I firmly disagree with with the consequences of that strategy.
One of the hardest aspects of development for me has always been anticipating the code I’m going to need to write to solve a problem. BDD saves me from the hassle.
Stakeholders may or may not care about cucumber scenarios, but there is still value in having developers write them.
Nobody knows how to organize cucumber features and steps. Every project has it’s own conventions–that is, if it has conventions at all. Here is a pattern that works for us.
Although they’ve been around for a while, very few people know that factory_girl comes with some really useful cucumber steps.
Cucumber steps are meant to be reused. Keep them generic so you don’t have to work too hard.
We love Cucumber but often see it poorly used and misunderstood. We are beginning a blog series about “Practical Cucumber” to give you tips and tricks and keep you out of a pickle.
“I don’t have time to test” seems to be somewhat of a recurring theme in hurried projects. Stop lying to yourself—and your clients.