nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

Normally, one would expect Assert.Throws to be used with one of the
methods under test rather than with a test method. Nevertheless, it
seems useful to give more info about the exception that was actually
thrown.

** Changed in: nunitv2
       Status: New => Triaged

** Changed in: nunitv2
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of NUnit
Developers, which is subscribed to NUnit V2.
https://bugs.launchpad.net/bugs/800089

Title:
  Assert.Throws() hides details of inner AssertionException

Status in NUnit V2 Test Framework:
  Triaged

Bug description:
  NUnit 2.5.9.10348

  If AssertionException happens in a delegate provided to
  Assert.Throws() the diagnostic message does display no details making
  it hard to know which of asserts failed:

  Test 'Test.Issue' failed: 
    Expected: <System.InvalidOperationException>
    But was:  <NUnit.Framework.AssertionException>

  instead it would be good to display the assert message if
  AssertionException was thrown like:

  Test 'Test.Issue' failed: 
    Expected: <System.InvalidOperationException>
    But was:  <NUnit.Framework.AssertionException> ("Cannot start with zero")

  plus the inner stack trace. Please see the test attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nunitv2/+bug/800089/+subscriptions