Activity log for bug #532536

Date Who What changed Old value New value Message
2010-03-05 10:27:43 Petr Kuzel bug added bug
2010-04-15 03:23:22 Charlie Poole nunitv2: status New Incomplete
2010-10-30 18:47:30 Charlie Poole nunitv2: status Incomplete Won't Fix
2010-11-02 21:09:53 Charlie Poole bug task added nunit-3.0
2010-11-02 21:12:52 Charlie Poole tags feature framework
2010-12-05 18:16:12 Charlie Poole nunit-3.0: status New Confirmed
2010-12-05 18:16:20 Charlie Poole nunit-3.0: importance Undecided Medium
2013-10-11 04:06:49 Charlie Poole bug task deleted nunitv2
2013-10-19 05:09:48 Charlie Poole tags feature framework github
2013-10-19 05:11:58 Charlie Poole 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. [Issue now tracked at https://github.com/nunit/nunit-framework/issues/18] 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.