We’ve just added a new blog post about tests and testing:
For a long time we’ve (and by “we” I mean the industry) harped on test coverage. We’ve sold each other the idea that tests are the safety net developers need to code without fear. Because if the tests pass, your changes must be good, and ready for production, right? Advocates of Test Driven Development even say you should write the tests before the code. But what happens when the tests are wrong? When they’re buggy? When they don’t test what you think they do, or worse don’t test anything? In short, how do you test the tests?