Awesome, but only when used by a disciplined coder. I particularly detest the types who think they don't need to document anything because they have unit tests.
Also, people who act like unit testing is some religion need to shuffle off this mortal coil post haste.
Name:
Anonymous2006-04-26 9:51
I love the types that think unit tests are a substitute for documentation and proofing. 3 months later, they're wondering wtf they're actually testing.
Name:
Anonymous2006-04-26 11:12
Unit testing is cool, but some things are really painful to test for. Take a database job for instance; you'd need to write creation code for creating the database from scratch, run the test (which, being that this would be a real transactional database, could take hours and is thus not something you can set your VCS to do after every commit) and then examine every affected row that consistency was retained and so forth. Not to mention that testing like this typically requires access to an external server, because you can't really do tests like this on your desktop if the database is xbox hueg.
Still, most of these problems are manageable. Just try convincing a "RESULTS! NOW! GODDAMNIT!" -oriented boss that it's worth spending time _testing_ things, when you could be writing that new cool thing. (And then you get reamed for delivering code that doesn't work.)