-
Notifications
You must be signed in to change notification settings - Fork 325
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
How did I get myself into a place where Microsoft Testing Platform mode is always enabled with dotnet test
?
#10605
Comments
If it's useful information, we're currently linked against the 1.4.3 versions of the Microsoft Testing Platform libraries. |
Apparently there is something amiss in my stock test project that I use for reproducing issues. 🤦🏼 Starting over with I would still love to know how my project got into this "MTP is always enabled" mode. I can package it up if you want to try to figure it out, because I'm at a bit of a loss. |
Repro project: vstest-10605-repro.zip I was running |
dotnet test
back with .NET SDK 8.0.404?dotnet test
?
In the repro, you have |
I'm trying to reproduce a problem with xUnit.net v3 for someone who is using
dotnet test
, but since installing .NET SDK 8.0.404 (dotnet test --version
reporting17.11.9.46202
) it appears that there's no way to disable its recognition and usage of Microsoft.Testing.Platform-compatible test projects, so I'm unable to run tests the same way as users do (that is, throughxunit.runner.visualstudio
and the TPv2 APIs).Another way to say this is:
<TestingPlatformDotnetTestSupport>true</TestingPlatformDotnetTestSupport>
is no longer required, and in fact, trying to set the value tofalse
does not turn off MTP support.Is there any way for me to get the old behavior back, short of creating a VM and installing an older SDK in it?
This is actually about more than just me reproducing this one bug, though. Users will see
dotnet test --help
and virtually everything on that screen will be wrong because those command line options do not apply when running a Microsoft.Testing.Platform project. How is the user to know this will be the case? How can they get an accurate set of command line options fordotnet test
now?Edit: this turns out to be a local problem that I don't understand but I wouldn't mind help understanding anyways.
The text was updated successfully, but these errors were encountered: