-
Notifications
You must be signed in to change notification settings - Fork 80
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
Explicit parameter from xunit.v3 not working in Visual Studio Test Explorer #412
Comments
Thanks! I'll take a look. |
I've been thinking about how to interpret the "gesture" the user makes here, since Test Explorer doesn't have any knowledge of explicit tests, so there's no way to know exactly what the user has asked to do here. I believe that where I landed is this, and let me know what you think. If the user has asked to run specific tests, that may mean they did something like "please run this one test as it's explicit", or it could also mean they said "please run all the tests in this one assembly" and Test Explorer decided to hand back the full set of tests. Therefore: if the requested test list is entirely explicit tests, then we will run them; if the test list includes both explicit and non-explicit tests (aka, the "run this class" or "run this assembly" version), then we will only run the non-explicit tests. What do you think of this interpretation @vbreuss? |
I think this is a legitimate interpretation, @bradwilson and also similar to the implementation in NUnit, as expressed in this comment:
In my project, I currently use NUnit for some special case tests to activate/deactivate certain features and had to introduce a dummy test without the |
Fixed in Note you will also need to pick up |
Thanks for your effort, @bradwilson. I tested the updated packages and it worked as expected! |
Explicit tests are never run in the Visual Studio Test Explorer, regardless if a single test, a test class or all tests are selected to run. This affects both
Fact
andTheory
attributed tests.I created a repository to reproduce the issue here, but basically it's adding the following test and trying to execute it in VS:
The text was updated successfully, but these errors were encountered: