I test as much as I can, for two reasons:
- I have found the weirdest stuff break, stuff I would never have imagined.
- It's a form of documentation, for those of us without documentation sections in our non-existent project plans.
The only warning I'd have is that whenever a test fails, you have to make sure it's testing what you want it to. Recently, I made a necessary non-backwards-compatible interface change. Worked fine. Then, I started using it. Made a few more changes, then BAM! a test started failing. I looked deeper and found it was a test I hadn't updated when I made my interface change. The test hadn't been testing what I thought it had.
We are the carpenters and bricklayers of the Information Age.
Then there are Damian modules.... *sigh* ... that's not about being less-lazy -- that's about being on some really good drugs -- you know, there is no spoon. - flyingmoose