Pimp your VSTT exception tests

Dew Drop - July 31, 2008 | Alvin Ashcraft's Morning Dew

Dew Drop - July 31, 2008 | Alvin Ashcraft's Morning Dew — Thu, 31 Jul 2008 17:39:24 GMT

PingBack from http://www.alvinashcraft.com/2008/07/31/dew-drop-july-31-2008/

re: Pimp your VSTT exception tests

marinosc — Thu, 31 Jul 2008 21:57:36 GMT

I definitely agree with this approach to exception testing. It's very easy to implement, saves you a bunch of duplicated code, and allows you to specify the exact line of code that you expect the exception to occur on. I actually wrote a very similar blog post to this one in early June:

http://srtsolutions.com/blogs/chrismarinos/archive/2008/06/06/testing-for-exceptions-in-unit-test-frameworks.aspx

re: Pimp your VSTT exception tests

ddietric — Thu, 31 Jul 2008 22:36:50 GMT

Hey Chris! I hadn't seen your post before. Thanks for stopping by and sharing! There is one interesting difference though: I noticed that instead of catching all exceptions and then performing a type comparison you have a catch block handling the exceptions of the type passed in as the type parameter which immediately returns. This means that your tests will also pass if the exception type thrown is derived from what you expected. I wonder if this has caused any false positives?

D.C.

VSTS Links - 08/04/2008

Team System News — Mon, 04 Aug 2008 18:05:35 GMT

Jeff Levinson on What Can You Use TFS For? Eugene Zakehareyev on Work Item Customization tidbits: Special...

The ultimate ExceptionAssert.Throws() method

Dennis "D.C." Dietrich — Wed, 07 Jan 2009 10:17:57 GMT

A while ago I published a post titled Pimp your VSTT exception tests in which I pointed out some disadvantages