[Nunit-core] [Bug 532536] Re: ExpectedException specification

2013-10-10 Thread Charlie Poole
** 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

[Nunit-core] [Bug 532536] Re: ExpectedException specification

2010-12-05 Thread Charlie Poole
** Changed in: nunit-3.0 Status: New = Confirmed ** Changed in: nunit-3.0 Importance: Undecided = Medium -- 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:

Re: [Nunit-core] [Bug 532536] Re: ExpectedException specification

2010-11-02 Thread Charlie Poole
Yes, you are correct. NUnit didn't always recognized derivatives of its attributes because we reflect on the attribute name. However, we started descending the inheritance chain for selected attributes in 2.5 and after a recent bug fix to ExplicitAttribute, I believe all of them are recognized.

[Nunit-core] [Bug 532536] Re: ExpectedException specification

2010-11-02 Thread Charlie Poole
For NUnit 3.0 we should re-address this. Options... 1) Allow multiple ExpectedExceptionAttributes on a method, where any of the given exceptions satisfies the test 2) Verify that only one ExpectedException is present and give an error if there are more This may apply to other attributes as

[Nunit-core] [Bug 532536] Re: ExpectedException specification

2010-04-14 Thread Charlie Poole
** Changed in: nunitv2 Status: New = Incomplete -- ExpectedException specification https://bugs.launchpad.net/bugs/532536 You received this bug notification because you are a member of NUnit Developers, which is subscribed to NUnit V2. Status in NUnit V2 Test Framework: Incomplete Bug