-
Notifications
You must be signed in to change notification settings - Fork 727
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
Labels
Milestone
Comments
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
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
Nobody has picked this up and nobody else has asked for this so closing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
The text was updated successfully, but these errors were encountered: