Great points. What not to test is just as important as what to test. If you're interested in learning how to start TDD, Typemock is hosting a free webinar next week introducing TDD: http://j.mp/IVmQNi

This is just one more reason why it's important not to skimp on developer testing, including unit testing (of course they need to include these scenarios in their test cases). Learn how to prevent these cases at http://j.mp/IdJI0j

There's a lot of misconception about tests. If you're interested in how to start unit testing, check out this tutorial on Wednesday: http://j.mp/HPguPs

My biggest problem is this equates Agile to Scrum, pair programming, and open floor plans.

Agile is also dev practices: refactoring, TDD, unit testing, continuous build, etc. Agile = faster development and accelerated deliverability. Sure, cooperation and breaking down silos is part of it but introverts can unit test. (Learn more: http://j.mp/Hex2Uy)

Testing is a pain and it takes time. Plus, we don't always even find the bugs. But if you write unit tests or want to start unit testing, Typemock's newest release (released last Monday) makes unit testing easy and finds the bugs for you. http://www.typemock.com