Comment 2 for bug 957899

I think ExpectedException is used for Assert.Throws(), not Assert.DoesNotThrow() isn't it?

Knowing the type of exception alone, though, often isn't enough to diagnose an unexpected failure. You need details. Without them you have to modify the test code to catch the Exception - which, in turn, opens it up to failure.

Currently, DoesNotThrow() prints "Unexpected Exception: {0}", ex.GetType(). Instead, it could just convert the exception to a string and provide complete details.

Throws() would probably also benefit from this.