Debugging MSTest in Visual Studio 2017.3 (15.3): 'Inconclusive: Test not run'

In case you have 'Inconclusive: Test not run' status for MSTest tests when you launch "debug" for a unit test in ReSharper 2017.1.x, please install the latest ReSharper 2017.2 release build  

Related request on YouTrack:

13 out of 22 found this helpful

Visual Studio 2017 15.5.2

ReSharper 2017.3.1, built on 2017 December 21

Still facing the same issue


Same issues as everyone else. Using VS Community 2017 15.5.2 and Resharper 2017.3 EAP 9. I am experiencing the following problems:

  1. Running tests results in all tests marked as inconclusive.
  2. When I can run the tests and I try to debug a single test, the debugger does not stop at breakpoints.

I am under a time crunch and working on a huge solution or I would try to get you a sample that fails.


Yes, I can confirm the EAP build fixes the issue. Thank you team!


Issue came back with new visual update (Inconclusive: Test not run). In UnitTestSession window I can see an exception:

ERROR Transition failed: Transition from state <HandShake> on event <remote::.ProtocolVersion>. Cause: System.InvalidOperationException: Test-cases are missing for the selected tests. Did discovery succeed?

Is there any permanent solution for this? Previous EAP worked until next update.


Visual Studio Professional 2017 15.4.3

Resharper Ultimate 2017.2.2


Having the same problem with VS Professional 2017 15.5.2 and Resharper 2017.2.2. This is a serious bug !

Edited by Milan Milanovic

The same issue in VS 2017 15.5.1 and Resharper 2017.2.2
In 15.4.5 everything was ok.


@Maria, R# team - currently using VS 15.5.4 with .NET framework 4.7.02556 and receiving the error "Inconclusive: Test not run" for all MSTest and XUnit tests. I believe this issue only started recently when upgrading to R# 2017.3.1. I have checked the Test Setting File workaround suggested by Won Lee above and this does not work for me.

Are we any closer to releasing a fix? Thanks


I'm new to .net so might be wrong.. I think the reason id did not work for me is that I had not installed the correct runtime/sdk, like in my comment above. The .csproj file contains a line like this: <RuntimeFrameworkVersion>1.0.4</RuntimeFrameworkVersion> within the <PropertyGroup>. I think this needs to match with an installed runtime. I have the NetCore.App version 1.0.5 installed, along with SDK version 1.0.4. And the RuntimeFrameworkVersion is 1.0.4. 


Alexander, Maria has been working with me to troubleshoot the issue. Here's the link to the support request. I have provided a sample solution and a verbose log file.



Alexandr & Maria, i've sent you an email with explainations and sample solution


@Mathias Johansson, please follow this guide to upload it to our servers.

@maxim.shlain and @Won Lee Thanks a lot! We are looking into it.


For me, with some projects, the cause was having a file path to a settings file which no longer exists in the following setting. Thanks Maria in Support for pointing me to it.

ReSharper | Options | Tools | Unit Testing | MsTest

I still have the same issue with other projects however. Microsoft has released debugging related fixes recently although even the latest version, 15.5.4, doesn't seem to address the issue.

Edited by Won Lee

@Alexander: I have now uploaded (HTTP) a trace for Inconclusive error. Filename is "". Let me know if there's anything else you need.


Hi there!

Yes, as @Won Lee said, a non-existent setting file can be one of the reasons why you get "Inconclusive" message (thanks to @maxim.shlain for help): The fix will be available in the next bugfix - 2017.3.2 (end of January).

@Mathias Johansson, thanks, got it! We need some time to analyze.


@Maria, @Alexander: I can confirm that @Won Lee's fix by clearing the Test Setting file field in ReSharper Options works since the file that was specified does not exist.


For me, it workes after installing NETCore.App version 1.0.5. Can be downloaded here:

(I used the Windows 64-bit SDK Installer)

I only had version 1.0.0 and version 2.0 installed before and it was expecting 1.0.5 for some reason. 


@Mathias Johansson, nice to hear that!

@Philip Barnes, could you please submit a request via and provide a log file? Please run Visual Studio with the command line 'devenv /ReSharper.LogFile C:\log\resharper_log.txt /ReSharper.LogLevel Verbose', reproduce the issue and send us 'resharper_log.txt' file. Thanks!



I also have this issue with latest updates (as of today).  I can try and supply log file if that will help.

I had nothing in test settings.

For other users, disabling MsTest support in this screen at least allows me to use VS to debug these tests :)





I get this problem too, using Resharper 2017.3.2.. It works for most my projects, but in this single one all the tests fail with the "inconclusive" failure and no information about why.

All my tests work in the VS default test runner, and if I turn the test project into a console app and write my own test runner to monitor unhandled exceptions and first chance exceptions, I still don't see anything critical, and my tests run through with my console app test runner.

There's probably some issue with the project, but without a failure message to go on, and not being able to reproduce it outside of resharper test runner, it is pretty daunting to guess at the error.

Could you make an error message for what inconclusive means so we have a chance of tracking down the failure?

I'm guessing the issue is related to dependencies on this WebApi project. I initially got some .dll conflicts which showed up in VS test runner and my own console test runner, but when I got those fixed and green, resharper was still showing inconclusive. And I've tried on other computer and with manual cleaning of all temporary files, with newest version of VS professional and resharper.

Edited by Hakon Humberset
I'm having the same problem to run any test using NUnit framework. "Inconclusive: Test not run"

Visual Studio 2017 15.5.6

ReSharper Ultimate 2017.3.3  Build 111.0.20180302.65130


---------- SOLVED Adding project dependency to Microsoft.NET.Test.Sdk --------------




Edited by Jukarox

I am still trying to run tests using ReShaper in VS2017 and they do not execute and no message is displayed VS 2017 Version 15.6.5 and ReSharper Ultimate 2017.3.5.

Has this problem been solved? 


@Ashton Judson, the problem that was known to us in January was fixed in R# 2017.3.2. Probably, you're facing some other problem.

What type of project do you use? Is the problem reproduced in all solutions, even in newly created one?


@Alexander Kurakin, 

It happens in all projects even new ones.



I have a simliar problem with R# 15.7.27703.2000 and Visual Studio 15.7.1. Tests are inconclusive and I can't debug the tests (no breakpoints are hit, the test just run throu).


I'm running Resharper 2018.1.4, and Visual Studio Enterprise 2017, version 15.7.27703.2047. I found that using Nuget package 'MSTest.TestFramework' causes unit test not to appear in Unit Test Explorer, and give 'Test inconclusive' issues, too (at least version 1.1.11 does, haven't tried other versions). Using Visual Studio's own dll-reference does work, though. C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\PublicAssemblies\Microsoft.VisualStudio.QualityTools.UnitTestFramework.dll


@Alex Maskaev Please try installing R# 2017.3 EAP build and check the same behaviour once again.


I can also confirm that the EAP build fixed the issue for me. Thanks again!


Just to be more specific, 2017.2 EAP 13 fixed this issues for me. EAP 12 was still broken.


I had the same issue even with Resharper 2017.2.1 in Visual Studio 2017 (v15.3.5). I think I got Rehsarper updated first, then I updated Visual Studio to 15.3.5 .

To fix issue, I had to re-install Resharper 2017.2.1 - I just clicked on "Rehsarper \ Help \ Check For Updates ..." , then unsinstall and reinstall.


It is working fine now.


Hi there,

Same for me, the issue came back with the last VS Update

Visual Studio Enterprise 2017 15.4.3

Resharper Ultimate 2017.2.2


Please sign in to leave a comment.

Have more questions?

Submit a request