Replies: 1 comment
-
Earlier we had an automatic category called Explicit, but it doesn't work as it should after the latest changes. We have also talked about adding a specific keyword, e.g. Explicit, that would sort of do what you propose. What tends to be problems around these things, are when such keywords are being used together with other filters, but I guess we could add one and in the first round just let it work independently, and then fix the combinations later on. I'll see if we can get this in the next version. The current workaround would be to manually add a category to these tests that could be used as a filter. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have been googling, but have not found an answer for this.
I have a test suite with a number of tests that are marked with the
[Explicit]
Attribute.When I run
dotnet test --project **/*.Tests.csproj
in my CI pipleine this does not run explicit tests (as I would expect).Is there any argument to include explicit tests in a Command Line run that I have missed?
Thank you!
Using NUnit 3.12, NUnitTestAdapter 4.2.1
Beta Was this translation helpful? Give feedback.
All reactions