More tests are not always good – Why you should stop at 100%
test coverage  As I started in the programming industry almost a
decade ago, writing tests at all was still a fairly new thing
for many developers. Having been one of the early TDD advocates
in my social environment, I had to recommend many best practices
and books to students and colleagues. Kent Beck, Robert Martin
and many other more or less public figures provided invaluable
advice and did a lot of persuading with their books and talks
and they continue to do so. Today I enjoy a situation where you
almost have to justify every test you don’t write.  The basics –
Why should you write tests?FirefoxScreenSnapz070 More tests are
not always good   Why you should stop at 100% test coverage  In
order to see which tests you should not write, we first should
clarify why tests are good. Tests are a powerful tool to    •
Guard against regression   • Provide documentation  These are
the two main reasons for tests that will make your project fly,
and they ar