nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

I'm adding this back to NUnitV2 as well as 3.0. We'll implement it in
the 2.5.9 release.

Planned changes...

* All NUnit attributes will have the AttributeUsageAttribute Inherited named parameter set explicitly.
    * Attributes intended to provide a unique value will use Inherited=false. For example, NUnit 
      can only deal with one description per test, so Description will not be inheritable.
    * Attributes that can have multiple values, like Category, will use Inherited=true
    * Attributes that can be reused with no problem, like Explicit, will use Inherited=true
    * In spite of the above, any attributes for which there is a possible breaking problem, will use Inherited=false

* NUnit will fetch attributes using GetCustomAttributes(true), which will retrieve any base class
  attributes that have Inherited=true and ignore those with Inherited=false. (This is a change,
  so it's the place where we will see any breaking problems.)

Charlie

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

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

** Changed in: nunit-3.0
   Importance: Wishlist => Medium

** Changed in: nunitv2
     Assignee: (unassigned) => Charlie Poole (charlie.poole)

** Changed in: nunitv2
    Milestone: None => 2.5.9

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

Status in NUnit Test Framework: Triaged
Status in NUnit V2 Test Framework: Triaged

Bug description:
The attribute Category (used for making tests as being in a particular category) should be inherited. This would allow setting up an abstract base class for a certain type of test, marking it as [Category("Whatever")], and having NUnit recognize that every other test that inherits from that class is also in category "Whatever".

As of 2.5.7.10213, CategoryAttribute is not inherited.