Why Steak over Cucumber (for Ruby acceptance testing)(gist.github.com)
gist.github.com
Why Steak over Cucumber (for Ruby acceptance testing)
https://gist.github.com/770894
3 comments
Another reason:
I find it hard to connect certain given/then/when to the relevant steps in larger projects.
But maybe that's just me :) Any ideas around that would be appreciated.
I take it in steak you just call a general method. Just do a find in project and bom :) there it is. It's harder with steps (longer sentences) I guess it is doable though...
I take it in steak you just call a general method. Just do a find in project and bom :) there it is. It's harder with steps (longer sentences) I guess it is doable though...
[deleted]
I disagree. Language shapes thinking to a certain degree, and Cucumber can help put yourself in a useful mindset for describing specs.
I think he has a point with the last comment though, most (though not all) of the benefit comes upfront. Mind you, that's the best place to have a benefit :)