nunit-core team mailing list archive
-
nunit-core team
-
Mailing list archive
-
Message #02650
[Bug 957899] Re: Feature: Assert.DoesNotThrow() needs exception details
Here is an example:
FileNotFoundException ex = new FileNotFoundException( "invalid path", "/path/to/nowhere" );
Console.WriteLine( ex );
Assert.DoesNotThrow( delegate { throw ex; }, "file test" );
The Console.Write displays:
System.IO.FileNotFoundException: invalid path
File name: '/path/to/nowhere'
The Assert.DoesNotThrow() displays:
file test
Unexpected exception: System.IO.FileNotFoundException
I think the details of the exception are important for debugging an
application.
--
You received this bug notification because you are a member of NUnit
Developers, which is subscribed to NUnit V2.
https://bugs.launchpad.net/bugs/957899
Title:
Feature: Assert.DoesNotThrow() needs exception details
Status in NUnit V2 Test Framework:
New
Bug description:
NUnit 2.5.10 11092 (Windows)
When Assert.DoesNotThrow() actually does throw an Exception, the
Errors and Failures window of the GUI does not show any details about
the exception. Rather, it just shows the provided text parameter and:
Unexpected exception: NUnit.Framework.AssertionException
It would be handy if the Assert would also show details about the
Exception being thrown. Otherwise, test code has to be changed to
find out what went wrong.
Thanks.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nunitv2/+bug/957899/+subscriptions
References