Economy Size Geek

Quality Tree Software, Inc. - Better Testing, Worse Testing

This leads me to my next general conclusion: an isolated improvement in one aspect of a development process tends to be offset by declines in another, resulting in no overall improvement in the final result.

This is an interesting idea - both because I’ve spent a lot of time in the last few weeks teaching about how to use all the testing tools available to Rails developers so I’ve been thinking about all the different ways you can test.

But more importantly, I have experienced it myself. Once you start getting really good coverage from your unit tests and things really start cranking it can take a special amount of will to really sit down and add in all the Selenium tests that the system should have.

The last project I released had very few bugs. All of them were in areas where the testing was spotty or incomplete.
So remberer - test early and often - but also test from a variety of perspectives - or you will just push your bugs from one place in the code to another.