nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

It would be great if someone else could also try this and verify the
problem.

The proper behavior - as designed - is that use of /exclude alone
(without also using /include) should _not_ cause any explicit tests to
be run. This behavior was introduced some time back and has worked for a
long time but it's possible that some recent changes have caused a
regression.

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

Title:
  Explicit test runs if /exclude parameter is used

Status in NUnit V2 Test Framework:
  New

Bug description:
  Assume we have the following test fixture:
  [TestFixture]
  class Test1
  {
      [Test]
      [Category("Negative")]
      public void SomeNegativeTest()
      {
          // ...
      }

      [Test]
      [Explicit]
      public void SomeExplicitTest()
      {
          // ...
      }
  }

  If one runs nunit.exe against this test fixture using
  '/exclude=Negative', the explicit test runs. The same issue appears
  when Negative category is excluded manually in UI.

  UPDATE:
  NUnit version: 2.6.0.12051

To manage notifications about this bug go to:
https://bugs.launchpad.net/nunitv2/+bug/1006604/+subscriptions