Quick question:
Usually I'm in the habit of putting a try-catch block around code "just for the heck of it", especially if that code contains a call to an external 3rd-party library. This seems like a good practice to make sure all exceptions are handled gracefully. However, when unit testing and trying for 100% coverage, it has presented a problem in that often I can't really come up with a test that will exercise the exception handler. This leads to < 100% coverage, which is a pain and does not make for nice round numbers in coverage.
Any suggestions?