Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Category inclusion/exclusion is ignored when it comes to SetUpFixtures #39

Closed
CharliePoole opened this issue Oct 28, 2013 · 1 comment
Closed

Comments

@CharliePoole
Copy link
Contributor

In my DLL there are a few TestFixtures, divided to various categories with the Category attribute.
There's also one SetUpFixture that has a global SetUp method, and it's marked with Category("OneCategory").

When I run nunit (either console or GUI) with "/include=OneCategory", the global SetUp method runs, followed by all tests from OneCategory. This is great. However, when I run nunit with "/include=OtherCategory", the same global SetUp method still runs - followed by all tests from OtherCategory. Adding an explicit "/exclude=OneCategory" doesn't seem to help either.

I'd expect that category inclusion and exclusion would also affect the SetUpFixtures that run, not only TestFixtures that run.

See comment at https://bugs.launchpad.net/nunit-3.0/+bug/616226

rprouse added a commit that referenced this issue Sep 1, 2014
@CharliePoole CharliePoole added this to the Future milestone Feb 21, 2015
@CharliePoole CharliePoole modified the milestones: Future, Backlog Dec 4, 2015
@CharliePoole CharliePoole removed this from the Backlog milestone Jul 25, 2016
johnmwright pushed a commit to johnmwright/nunit that referenced this issue Oct 28, 2019
johnmwright pushed a commit to johnmwright/nunit that referenced this issue Oct 28, 2019
… ref nunit#39, updated to 1.1.0.7 and set longrunning tests to explicit
johnmwright pushed a commit to johnmwright/nunit that referenced this issue Oct 28, 2019
@rprouse
Copy link
Member

rprouse commented May 1, 2021

Nobody has picked this up and nobody else has asked for this so closing.

@rprouse rprouse closed this as completed May 1, 2021
@rprouse rprouse added this to the Closed Without Action milestone May 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants