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
I've also blogged a lot about how to use Cucumber well here:
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
I've also blogged a lot about how to use Cucumber well here:
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.