Tracking Exceptions while Testing

Tracking exceptions up the Call Trace lets you see where a test failure starts and to visually see how far an exception ‘leaks’ up your call stack before being handled.

The little indicates which calls exited via an exception, as opposed to exiting normally out the bottom of the function, or through a return.

You can double click on any call in the Trace and navigate there in the editor. And — you’ll see the error fingers in the gutter if this exception exited all the way out of your test case.

You can right click on the fingers and navigate up and down the exception stack trace. This feature is available even without profiling being on, as it intercepts exceptions coming out of the test engines and saves that metadata along with the test. Very handy for tracking down why a test failed.

  Permalink |  Comments[0]

Recent Entries

 » Build 2687 Posted
 » New Unit Testing Book
 » Build 2293 Update Posted
 » Microsoft Team System NUnit Adapter
 » MS Team System Test Support

You can leave a response, or trackback from your own site.

Leave a Reply


You must read and type the 5 chars within 0..9 and A..F, and submit the form.


Oh no, I cannot read this. Please, generate a