3 ms·

It completely depends how you use it. There's so much misuse of it out there I can understand why people hate it so much. But done right it's an extremely valua

It completely depends how you use it. There's so much misuse of it out there I can understand why people hate it so much. But done right it's an extremely valuable collaboration tool. I'd recommend the Cucumber Book if you want to read about how to use it well: http://pragprog.com/book/hwcuc/the-cucumber-book http://pragprog.com/book/hwcuc/the-cucumber-book I've also blogged a lot about how to use Cucumber well here: http://chrismdp.com/tag/cucumber http://chrismdp.com/tag/cucumber

lotyrin 13y ago
Yeah. Just about everyone I've run into using Gherkin-based testing seems to think it's for step reuse, or for covering code, or for integration testing. Those are different kinds of tests. Go write them in a unit or a spec or whatever you feel like. Code coverage - covering your ass during refactors - and integration - covering your ass before deployments - are just for you and can skip the regexp. Gherkin is for collaborating with my customer and making them tell me what the fuck they actually want. 90% of the value happens before any of the steps are ever implemented. A few user interactions will be covered, likely not even all of the possible ones. Little step reuse as focus is on readability. It's a really specific problem, and so far I haven't seen a superior option aside from Gherkin.