Menu
I have an issue very similar to this one.
Debugging any test in Resharper returns "Inconclusive: test not run". This occurs for every test, every solution, every project at my machine. Reinstalling VS2019 and Resharper didn't help. Running tests works fine.
I've debugged test using devenv.exe /ReSharper.LogFile C:\temp\resharper.log /ReSharper.LogLevel Verbose command and the result is this (a fragment of ~6900 lines file).
The first error says: “Method 'StartSessionAsync' in type 'ReSharperAwareWrapper' from assembly 'JetBrains.ReSharper.UnitTesting.MSTest.Provider, Version=777.0.0.0, Culture=neutral, PublicKeyToken=1010a0d8d6380325' does not have an implementation.”
I tried all the popular answers in the post I've linked and nothing seems to help.
Code is .NET Core 3.1 based C# solution.
Resharper: 2020.1.4 | Visual Studio: 16.7.0
337
If reverting to previous version then issue does not occur. Looking at the resharper log it looks like an Access Denied Exception attempting to start the tests so the tests never finish and hence the inconclusive/pending state. I'll submit the log file for review.
Upgraded Resharper to 2017.2.2 in VS 2017 version 15.3.4, and now debug of unit tests is not returning inconclusive. Another possible answer is to prevent VS from using test settings file. Located in "Test->Test Settings" menu. After changing branches it got enabled somehow without me noticing and tests stopped running.
If necessary, you can always re-run the tests that you executed last by clicking Repeat Previous Run on the toolbar, pressing Ctrl+U U or choosing ReSharper | Unit Tests | Repeat Previous Run in the menu. When the execution is over, the results are visualized in the Unit Test Sessions window.
As a workaround, you can launch test from VS Unit Test window, instead of Resharper's one. Thanks for contributing an answer to Stack Overflow! Please be sure to answer the question.
I've solved an issue by installing 2020 EAP version of resharper (2020.2 EAP). Seems like it's a bug in 2020.1.4 version.
120
I started to have exactly the same issue after i updated VS to 16.7. Funny thing is that it broke unit test debugging in Rider as well.
Microsoft has pushed new Microsoft.NET.Test.Sdk package, but looks like it does not help. As a workaround, you can launch test from VS Unit Test window, instead of Resharper's one.
30
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
