nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

What the bug reporter means is that an abstract test marked by a fixture
is not runnable and shows up as ignored with a yellow bar in the gui.
The tests I removed are still in the nunit-3.0 trunk, so it's still
doing ignoring abstract fixtures.

To accomplish this, NUnit has to pay ignore abstract fixtures (see
NUnitTestFixtureBuilder.CanBuildFrom and you have to change some code in
NUnitTestFixtureBuilder.BuildFrom to make the derived class work.

Since some of the same code impacts bug 487878, you may want to look at
that one at the same time.

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