nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

Oddly, in my tests, this only occurs when running the entire assembly
but not when selecting the test fixture and running it alone. However, I
can verify the bug.

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

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

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

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

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

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