-
Evan Light
3.8
Description:
Recently, in the Ruby community, there has been an upsurge of interest in testing. For instance, in the past year alone, we’ve seen the introduction of a bevy of new testing-related gems (i.e. context, cucumber, micronaut, factory_girl, webrat, etc.). These are all good things. And yet do we still see the forest for the trees? While testing improves code quality, facilitates refactoring, and eases debugging, these are not ends unto themselves. This point often seems to be lost as the “testing” drum is beaten ever louder in the Ruby community. This talk will attempt to engage the audience to rethink WHY they write tests and how to avoid some common pitfalls along the way.
Comments on this Talk
I love seeing live coding, it really pushes speakers to the edge, which is hard on them, but forces us to really see how they handle stress -- a learning opportunity. Any way, I think you might have been better off if you started by giving us the high level description of what you were going to work on. I also thought your comment to the comment that maybe the test framework should create a skeleton for you ("good idea, why don't you write it") was fair.
Great talk on BDD. The exercise might have been a little involved for the time frame that you had, but you were still able to showcase the importance of BDD and the process involved. I thought you handled audience questions/comments very well and had a good stage presence!