-
Notifications
You must be signed in to change notification settings - Fork 514
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
[dotnet] Unit test projects don't work #13319
Comments
I can reproduce. The underlying cause is that we create a self-contained app bundle, and getting that to work with This might be a start: microsoft/vstest#2200 (comment) but unfortunately that runs into another bug currently (#12572), so that might have to be fixed first. |
That vstest issue is related, but maybe not the same, not sure. In mac app case, the problem is not running vstest-console. It is ok to run it using dotnet. The problem is the host process that runs the tests, which is a different process started by vstest-console. This process is implemented in testhost.dll and started using "dotnet" by vstest-console. If I understand it correctly, what we need is vstest-console to start a testhost mac app that can run the tests. |
Any update on this? Should we expect this for .NET 8? I've managed to get some unit test coverage on code that interacts with macOS APIs by cross-compiling with MonoMac, but that's incomplete and not a great solution. |
@cyanfish we'll try to look into this for .NET 8 (but no guarantees we'll have time to actually fix it). |
Steps to Reproduce
Expected Behavior
Test project should run fine
Actual Behavior
Execution fails with "System.DllNotFoundException : Could not find the runtime library libxammac.dylib"
Environment
Build Logs
Example Project (If Possible)
NormalTest.zip
The text was updated successfully, but these errors were encountered: