Explicit test runs if /exclude parameter is used

[Vitalii Maklai]

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

[Charlie Poole (charlie.poole)]

What version of NUnit are you running? Some problems with Explicit
were fixed in 2.6, but it's also possible that new issues were
introduced.

Charlie

On Wed, May 30, 2012 at 10:31 PM, Vitalii Maklai <email address hidden> wrote:
> Public bug reported:
>
> 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.
>
> ** Affects: nunitv2
>     Importance: Undecided
>         Status: New
>
> --
> 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.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/nunitv2/+bug/1006604/+subscriptions
>
> _______________________________________________
> Mailing list: https://launchpad.net/~nunit-core
> Post to     : <email address hidden>
> Unsubscribe : https://launchpad.net/~nunit-core
> More help   : https://help.launchpad.net/ListHelp

[Vitalii Maklai (vmcl)]

Sorry, I forgot to mention the version: 2.6.0.12051.

[Charlie Poole (charlie.poole)]

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.

[Jv (jv-ravichandran)]

i would but i m not sure of the scenarios when /exclude or /include in a
positive/negative state makes a difference.

jv

On Wed, Jun 6, 2012 at 2:13 AM, Charlie Poole <email address hidden> wrote:

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

--
Regards,

Ravichandran Jv
http://ravichandranjv.blogspot.com

[Charlie Poole (charlie.poole)]

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.

[Charlie Poole (charlie.poole)]

This is fixed for the Gui, but I'm unable to reproduce it for the console runner following the steps given.