I admit it. I like my code to read like English when possible. I am not unique in that regard. But, at least as importantly, I like my tools to be tractable; I'm unhappy if a quick trip to a gem's /lib results in confusion and frustration. If I can't understand my tools, I can't extend them. I can't truly make them *my* tools.
In this regard, it is possible to have your cake and eat it too.
Because I, and many Rubyists, are test-obsessed, this talk will focus on testing tools. We'll discuss lesser known gems (in many senses of the word) that build on Test::Unit. Yes, we will compare them to the twin juggernauts of RSpec and Cucumber. Finally, if none of the existing tools quite scratch your itch, we will discsus how you can build tools that meet your particular needs without resorting to "Swiss Army Knife" tools.
By the end of this talk, you will develop an appreciation for tiny tools, some sympathy for Test::Unit, reach enlightenment, add a schizophrenic/demonic voice to your mind constantly asking you "why are you using THAT?", save a kitten, and just maybe learn a few things to change your testing practices for the better.
Evan Light (@elight) is a test-obsessed developer. The author of several rarely useful gems, out of frustration with Cucumber, he wrote Coulda: a lightweight Given-When-Then acceptance testing DSL that sits atop Test::Unit. When he's not a talking head at conferences, he's usually working at home as a freelance developer for one or more startups, working on open source, keeping his wife and four cats company, hacking nonsensically, talking at people on the internets, and/or attempting to lose weight (or any combination of the above). What else do you do when you live 3 hours from civilization?