-
joshua.clayton 3.51
Description:
Most Rubyists can agree that writing tests is a good thing; the benefits are many and the criticisms few. Although writing unit and functional tests first may help deliver a less buggy application, that application may not be exactly what a customer wants. Outside-in development driven by stories (written in Cucumber) will help guide iterations and client expectations while ensuring the application functions in the manner the customer expects.
Comments on this Talk
g33klady,
18 Apr 03:08 AM
got me even more stoked to try testing in Ruby with Cucumber
Delivery: Josh was friendly and confident. I only have 2 suggestions. First, at the beginning you were fiddling with your iphone a lot to switch slides and it was a bit distracting. Second, I would do less content on your slides. There were times where all you did is read what was on your slides. The less you put on your slides, the more people will look at you, which is a good thing as Josh has a great personality.
Content: Good points. Good balance of code and theory.
It may have just been the Ruby Brew, but this talk seemed like it was moving a mile a minute. Josh got off to a good start, taking the time to discuss a little bit about how and why we should write our tests--but seemed to degrade into a laundry list of testing tools. While I'm interested in seeing what software and techniques other folks are using, this just seemed way too fast for anything to really sink in. A little more focus would go a long way toward making this a great talk. And maybe pace it at more of an Isis, rather than a Discordance Axis ;)
Very nice discussion of Cucumber and how it addresses newer issues of handing JS.