Having an active community with lots of active developers and tons of blogs sharing code and setup might be considered great. And usually it is. But in case of cucumber I guess it was not always the best and therefore the removal of web_steps.rb in cucumber 1.1.0 is a huge and important step.
I have to admit, i never really liked cucumber! I t felt wrong and was annoying to maintain. So I sticked with rspec and integration testing was not really handled. But then I read the post The training wheels come off by Aslak Hellesøy and I finally understood why I did not like cucumber. I was writing code just not in ruby but some other language the web_steps file provided.
Checking other blogs about the release and common errors/mistakes people make when using cucumber I just started to rewrite my existing cucumber features and adding new ones. And It is fun: Clear and easy scenarios, clear and maintainable step definitions. I like!
And here a few more links which might come in handy:
- http://benmabey.com/2008/05/19/imperative-vs-declarative-scenarios-in-user-stories.html
- http://www.jackkinsella.ie/2011/09/26/why-bother-with-cucumber-testing.html
- http://dannorth.net/2011/01/31/whose-domain-is-it-anyway/
Cheatsheets for cucumber and capybara:
