Debug test results in 'Inconclusive: Test not run'


Visual Studio 2019
Version 16.7.1

xUnit 2.4.1

xunit.runner.visualstudio 2.4.3


Very simple test. If I 'run' the test, it passes


However, if I try to debug the test

I get Inclonclusive: Test not run


Restart vs, restarted computer etc...


I have similar behavior with NUnit (and also tested with xUnit) except while trying to run the test. The details of the warning stated:  "test was left pending after its run completion".

Microsoft Visual Studio Community 2019
Version 16.7.1

JetBrains ReSharper 2020.2 Build 202.0.20200810.170909

This just started after installing the latest version.  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.




What ReSharper version do you use? Please check the problem with the latest ReSharper 2020.2 -

If the problem is still there please start VS with the following command: devenv.exe /ReSharper.LogFile C:\log\resharper_log.txt /ReSharper.LogLevel Verbose, reproduce the issue and send us resharper_log.txt. Please share it privately via "Submit a request" form at the top of this page.

Thank you.




I have the same problem trying to debug NUnit tests in Rider 2020.1.4. I can run my tests fine, but when I attempt to debug them they all get marked Inconclusive: Test not run. I can debug the same tests just fine in Visual Studio 16.7.0 which doesn't have resharper installed.


The two warning messages I can see in the log are:


Element ... was left pending after its run completion.


Transition declined: Transition from state <v1.HostBinding> on event <remote::1.TestExecution.StatsChange>.

Hello Yarhamjohn,


Could you please try installing Rider 2020.2 - and check if the problem is still reproduced in it.

Thank you.


Hi Angelina,


Upgrading to 2020.2 appears to have fixed the issue, thanks!




Same, upgrading fixed it for me too


Confirming for anyone googling this: upgrading to 2020.2.1 fixes the issue of xunit test class being skipped while debugging!


This issue seems to be back.

Visual Studio Version 16.7.4/5 Resharper 2020.2.3

Can't run/debug tests that are targeting FullFramework 4.6.2. Get the same "was left pending after its run completion"

Test projects targeting .netcore3.1 seems to run and debug though.


Hello Jako Dewet,


Is there any chance you could provide us some sample solution in which the problem is reproduced?

Please also start VS with the following command: ``devenv.exe /ReSharper.LogFile C:\log\resharper_log.txt /ReSharper.LogLevel Verbose``, reproduce the issue and send us resharper_log.txt.

You can share all the info privately via "Submit a request" form at the top of the page.

Thank you.


Hi Angelina

I sent the log, but we have a big solution, with about 180 projects, some fullframework, some .netcore. We had multiple versions of the nUnitTestAdapter installed. I consolidated everything to 3.17 and it seems to solve the issue.



Upgrade to 2020.2.4 worked for me too.  So happy to have my R# back!


Had the same issue in Rider. Updated to Rider 2020.2.4 (202.7660.16), works fine again. Thank you!


I have one Solution that is now failing to run nUnit tests (it was fine but started failing today for no apparent reason).

All other solutions work fine but this one I get the amazing 

16:20:09.125 |W| Element <test> was left pending after its run completion.

Rider 2020.2.4


Got my tests working again, I updated a `ProjectReference` which broke the output of the project

<ProjectReference Include="..\someproject.csproj" >

I updated to the 2020.3 and it fixed the problem


I am using the latest version of ReSharper 2020.3.2 and still getting this issue.

I have tried turning on and off "Read solution model directly from project/solution files." and it has not helped.

Our solution is very complex with C++ and C# tests.  I got the C++ ones working by turning off the above flag but I cannot get the C# ones to run.  All tests run fine on our build server from the command line.

Everything was working fine in VS2017 but this problem has been a constant nightmare sine we upgraded to VS2019.

Any help gratefully appreciated.


Hello @Brian Hutchison!

In order to treat your case individually, please create a support request at Submit request

It also would be great if you collect "Verbose" ReSharper logs for the issue in accordance with How to run ReSharper with logging


I have same issue. I am using Microsoft Visual Studio Professional 2019 (Version 16.10.2), ReSharper 2021.1.3 and gtest-1.10.0

I've tried all the ways mentioned in this topic to troubleshoot this issue but not succeded.

The message I received is as follows:

2021.06.17 15:04:55.914   ERROR Child process exited with exit code "DLL not found"

--- EXCEPTION #1/1 [LoggerException]
Message = “Child process exited with exit code "DLL not found"”
ExceptionPath = Root
ClassName = JetBrains.Util.LoggerException
HResult = COR_E_APPLICATION=80131600
StackTraceString = “
at JetBrains.Util.ILoggerEx.LogMessage(ILogger this, LoggingLevel level, String message)
at JetBrains.ReSharper.Feature.Services.Cpp.UnitTesting.Execution.CppTaskRunner.ReportError(IUnitTestRun run, Exception e, Boolean showMessageBox, String message, String description)
at JetBrains.ReSharper.Feature.Services.Cpp.UnitTesting.Execution.CppTaskRunner.Run(IUnitTestRun run)
at JetBrains.ReSharper.Feature.Services.Cpp.UnitTesting.Execution.CppUnitTestRunStrategy.<>c__DisplayClass5_0.<DoRun>b__2()
at JetBrains.Util.Logging.Logger.Catch(Action action)
at JetBrains.ReSharper.Feature.Services.Cpp.UnitTesting.Execution.CppUnitTestRunStrategy.<>c__DisplayClass5_0.<DoRun>b__0()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()

2021.06.17 15:04:55.915 WARN Element MyVeryAwesomeTest.my_very_awesome_function_check was left pending after its run completion.

Could you help me to resolve it somehow?

Thank you in advance.


Please sign in to leave a comment.