Re:Testing with Cucumber – best practices
by jggkffkfjfjfjfj on Wednesday March 12, 2014 @02:09PM
(#7387219)
Best practise is to not use cucumber! By the time yoi have wanked away the afternoon writing stories, the client found a real developer who already coded the feature, leaving you - the failed liberal arts major, and now failed developer sobbing over your hipster hot beverage of choice.
[ Parent
| on HN ]
It's a lot of overhead for smaller shops or those with simpler requirements, and executable specs are only as good as the people who've written them.
Just the same, I've never seen a place use Cucumber as an integral part of their workflow.
Re:Testing with Cucumber – best practices
by mikesea on Wednesday March 12, 2014 @03:46PM
(#7387830)
I think, as with any tool, there's a time and place where it can be useful. Personally, I don't like to use Cucumber, but I've seen a couple of Rails apps that used it sparingly for integration tests and it worked wonders.