nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

** No longer affects: nunitv2

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

Title:
  ExpectedException specification

Status in NUnit Test Framework:
  Confirmed

Bug description:
  I subclassed ExpectedException attribute passing to super constructor
  AssertionException type.

  Now if I attibute my test method with both my subclass and
  ExpectedException(AssertionException) I get runner and attribute order
  dependent behaviour:

    - R# runner interpretes all attributes in sequence so a test method
  body that passes is toggled to failure by the first ExpectedException
  attribute then the failure is toggled back to pass by the next
  ExpectedException attribute.

    - Nunit 2.5.3 gui-runner seems to interpret just the first one

  for:

      <Test()> <ObservedBehaviour("Code generator produces duplicates.")> <ExpectedException(GetType(AssertionException))> _
      Public Sub ObservedBehaviourAfterChangeTest()

  yielding:

       Observed behaviour has been changed. Please balance the value of the change with compatibility breach costs.
       Originally observed behaviour: Code generator produces duplicates.
       NUnit.Framework.AssertionException was expected

  while for

      <Test()> <ExpectedException(GetType(AssertionException))> <ObservedBehaviour("Code generator produces duplicates.")> _
      Public Sub ObservedBehaviourAfterChangeTest()

  returning:

      NUnit.Framework.AssertionException was expected

  The documentation deserves a clarification.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nunit-3.0/+bug/532536/+subscriptions