nunit-core team mailing list archive

[Adam Connelly <adam.rpconnelly@xxxxxxxxx>]

I think I understand what you mean now. Is the difference that if the
class is abstract but not sealed, you assume that the intention is that
it will be inherited from as a base test fixture, whereas if it is
abstract and sealed you show a warning because it can't be a test
fixture?

-- 
Should not report tests in abstract class as invalid
https://bugs.launchpad.net/bugs/488002
You received this bug notification because you are a member of NUnit
Core Developers, which is the registrant for NUnit Framework.

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

Bug description:
Making a class abstract should be sufficient to indicate the test fixture is intended to be inherited by other concrete test fixture.

The problem occurs when the said abstract test fixture inherits from a 3rd party test fixture that already has TestFixture attribute, there is no way to avoid the warning now.

See http://groups.google.com/group/nunit-discuss/browse_thread/thread/b0d491a5df2e7897/3150383c3129273b