The supplied fix only deals with the anomalous behavior where Explicit
is involved. The overall pattern of how tests are selected using
categories is not changed and may need to be discussed further on the
nunit-discuss list in order to come up with a direction for NUnit 3.0.
** Changed in: nunitv2
Assignee: (unassigned) => Charlie Poole (charlie.poole)
** Changed in: nunitv2
Milestone: None => 2.5.6
--
[Explicit] does not get overridden if there is another category exclude
https://bugs.launchpad.net/bugs/548841
You received this bug notification because you are a member of NUnit
Developers, which is subscribed to NUnit V2.
Status in NUnit V2 Test Framework: Fix Committed
Bug description:
Steps to reproduce:
- Test code below ([1])
- nunit-console.exe <assemby.dll> /include=T /exclude=B"
Expected result:
- TestA() is executed
Actual result:
- No test is executed
Remarks
- Everything works as expected, if you remove the [Expected] attribute
[1] Test case
[TestFixture, Explicit, Category("T")]
public class Test
{
[Test, Category("A")]
public void TestA() { Console.WriteLine("-A-"); }
[Test, Category("B")]
public void TestB() { Console.WriteLine("-B-"); }
}
_______________________________________________
Mailing list: https://launchpad.net/~nunit-core
Post to : nunit-core@lists.launchpad.net
Unsubscribe : https://launchpad.net/~nunit-core
More help : https://help.launchpad.net/ListHelp
