Acceptance Testing with Cucumber
Acceptance Testing with Cucumber Presentation 1 [PDF]
Cucumber is all the rage these days, but many developers struggle to understand how and when to use it. It is designed to be an Acceptance Testing tool in the context of BDD, but that explanation tends to bring up even more questions.
In this tutorial, Aslak Hellesøy and David Chelimsky will help you to understand the role of Acceptance Testing, and how to use Cucumber effectively. Attendees will develop an app, working from the outside-in, using several different approaches to writing scenario steps and hooking them up to pre-existing and non-existing application code.
Update
This is going to be a hands on session in which you will all write code. To avoid clogging up the wifi during the session, please set up the following on your system beforehand:
- git
- rvm with ruby-1.8.7 installed with a clean gemset for our session
- the latest versions of rails-3.0.0.beta, rspec-rails-2.0.0.beta, and cucumber-rails
Note that we may be releasing new versions of cucumber-rails and rspec-rails as late as Sunday evening, so please check Monday morning before the session for the latest versions.
We’ll also post a github repository with additional material you’ll need. You’ll find it at http://github.com/dchelimsky/railsconf2010 on Sunday evening.
David Chelimsky
DRW Trading
David Chelimsky is the lead developer of the RSpec project, author of The RSpec Book, and also a software developer at DRW Trading.
Aslak Hellesøy
Comments on this page are now closed.


















Comments
I’ve had a love/hate relationship w/ cucumber for a year. It was great to see that my “hate items” have been addressed. The hands-on, while sometimes frustrating because of the network connections, gave me the benefit of pairing; although it was (thankfully) simple, it was still very helpful so see the various approaches on it.
I also appreciated the introductory part of the session; helps me get emotionally oriented to what the rest of the session will be.
Really good job.
Thanks to everybody who attended. We got a lot of great questions, and I hope you learned something valuable!
If you have suggestions about what to add/remove/change the next time we do this, please let us know here.
Aslak