A good developer today tests his or her own code. The old arguments—"It's too hard to set up," or "I don't know how to test my code"—just don't cut it anymore. Testing tools have never been easier to set up, configure, and use.
One community that has embraced testing is that of my beloved Ruby/Ruby on Rails. When Rails first appeared on my radar in late 2005, I was well and truly embedded in Java land. I wrote a lot of Java code, and I like to think that I was pretty good at it. But I didn't write many tests for my Java code; my method of testing essentially consisted of refreshing the browser a lot.
A Sad State of Affairs
You've probably said those same things to yourself at one point or another. You've rationalized your lack of testing. Well, no more. The cycle ends right here, right now.
Once I realized that I was writing the majority of my applications in CoffeeScript, I told myself that I needed to start testing this code like I did my back-end Ruby code. That led me on a hunt to find some great tools for the job.