On 26 Feb 2009, at 15:33, Tom ten Thij wrote:
We will be using Cucumber for a fairly large project. Are there any
areas that cucumber is lacking when there are many scenarios?
I believe the best candidate for showing our client the scenario
results is the html output. It strikes me that that becomes fairly
cumbersome to check with many scenarios. Methinks some javascript code
to hide all passing scenarios / features would be useful. Is there any
work being done on this?
In which areas could we help cucumber accommodate for large projects?
Tom.
Hi Tom,
At Songkick.com, we currently have 635 scenarios in our Cucumber
tests, and while we've had a few issues, the ROI has definitely been
worth it.
At the moment, IMO, the tools for feeding back the features to non-
technical people are pretty immature. My colleague Dan Lucraft wrote a
tool which produces a nicely-formatted PDF document from your features
folder[1] which is great, but won't work with the new version (0.2) of
Cucumber when it's released as the API against which such formatters
are written has undergone some significant changes for the new version.
Once this stuff stabilises into the 0.2 release I expect more effort
will be put into such tools, as the changes Aslak has made will make
it much easier to write them. Check out the brave vision for the new
HTML formatter:
http://rspec.lighthouseapp.com/projects/16211/tickets/178-design-the-html-markup-for-cucumber-02
Other than that, you'll be likely to hit some issues just to do with
managing the large number of specifications, but to be honest this has
surprised me by being much easier than expected. The amount of code
you actually write in the step definitions is minimal, especially if
you're using Rails and something like factory_girl, so with a bit of
regular re-factoring it's really easy to stay on top of it. We made a
call early on to split our features folder into sub-folders named
after the type of user, which has worked well for us:
e.g.
features/visitor/view_homepage.feature
features/user/change_password.feature
features/admin/list_users.feature
That's helped us to keep things tidy, but there are obviously other
ways to slice things up too. Are you planning to test the browser too
(with selenium / watir / etc) or just from the HTTP requests down?
Assuming you're building a web app of course... :)
[1]http://www.daniellucraft.com/blog/2009/01/features_report/
Matt Wynne
http://blog.mattwynne.net
http://www.songkick.com
_______________________________________________
rspec-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/rspec-users
