Quality Code with Cucumber
Cucumber’s plain text language for describing an application’s behaviour has become a popular tool for many Ruby and Rails teams. What’s all the fuzz about?
In this session you will see how Cucumber and BDD can be used on a real Rails project. You will learn how to install and run Cucumber and how to write features using Webrat and other related tools. I will also share my experience about how to write well-formed features and scenarios, and how to deal with common problematic situations.
The presentation will be in the form of a small, fast paced project, alternating between customer-team conversations and real-time programming with Cucumber and Rails.
People planning to attend this session also want to see:
Aslak Hellesøy
Bekk Consulting AS
I do Agile, Ruby and Java stuff. I wrote about a third of RSpec and most of Cucumber.
Comments on this page are now closed.
Comments
Audio is available here
Interview with InfoWorld here”:http://www.infoworld.com/d/developer-world/cucumber-hot-technology-developer-event-447
Good job! Well-presented in a professional manner. Interesting stuff. Just the right amount of jokes. I will try using Cucumber after being inspired by your talk!
I would have appreciated a 1/2 day tutorial.
Thanks for all the great feedback. I realise I only had 40 minutes (6:35 – 7:15), but had prepared for 50 minutes (thought it would start 6:25).
Come and ask questions at irc://freenode.net/cucumber or the mailing list if you have questions.
Tip for conference organisers: Make sure speakers get all the announced time ;-)
I’m new to cucumber -and this was a great introduction. I can see how developing this way can be addictive. I love the comment from twitter about it being testing crack.
Great talk. Would have liked to see it as a tutorial.
This was a very clear talk. I agree that it could have been longer. Nice slides!
Really good session by Aslak. This absolutely should have been one of the 1/2 day tutorials/workshops. Seeing/reading cucumber syntax is good, but you really only get a feel for it by watching it run and by writing and executing your own features and steps.
-Brian (aka. @Mac_Zealot)
Thanks for giving a “flow” overview first.