One of the most common causes of failures are cases that the programmer never considered. Once of my favorite test coverage tools shows you missed branches and

One of the most common causes of failures are cases that the programmer never considered. Once of my favorite test coverage tools shows you missed branches and I find that invaluable. My initial reaction was "oh no" but as I thought about it, this explicitly indicates that the programmer actually thought about a case. And is it any different than what most of us do in our unit tests? If we're expecting an exception that isn't thrown or the wrong exception is thrown, we force a test failure. One of the goals our team is working towards is more robust and complete metric and log collection. We specifically want to capture exceptions that make it to the application server for analysis, but this assumes that the developer has a) considered all cases and b) caught intermediate exceptions and continued processing (or abort).