nunit-core team mailing list archive

[Adam Connelly <adam.rpconnelly@xxxxxxxxx>]

Charlie, is this definitely a problem on the current trunk? I tried to
reproduce it (by making the same changes that you made to nunitv2) and
the test runner didn't produce any warnings. Also, you removed two tests
about not being able to run abstract fixtures and added two tests about
being able to run fixtures derived from abstract fixtures (more or
less). I couldn't see anything about warnings. My understanding of this
is that you still shouldn't be able to run abstract fixtures, but you
shouldn't get any warnings about abstract classes that are marked as
fixtures. Am I missing something?

-- 
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