36

How can I get Resharper to run tests in debug, when I get debug is "Inconclusive: Test not run"

Running any MsTest test in Resharper test runner is Ok, but if I try to debug, the R# test runner just displays Inconclusive: Test not run

This happens even with a simple test, e.g.

[TestClass]
public class BasicTests
{
    [TestMethod]
    public void Placeholder()
    {
        Assert.AreEqual(1, 1);
    }
}

But the build-in test runner in Visual Studio works for both just running and for debug

Additional info: It appears to be only happening in my VS 2017 preview instance !

Additional info: It also appears to be happening in my VS 2017 with the recent Update 3 !

SteveC
  • 15,808
  • 23
  • 102
  • 173
  • 1
    If you are using R# 2017.1.3 release build, it does not support .NET core 2.0 preview (automatically installed with VS2017 preview) - https://youtrack.jetbrains.com/issue/RSRP-464754. Try installing R# 2017.2 EAP build https://www.jetbrains.com/resharper/eap/ – Alexander Kurakin Jul 25 '17 at 08:54
  • @AlexanderKurakin Nope not using any .NET Core – SteveC Jul 25 '17 at 08:56
  • 2
    Just reproduced the issue you'd mentioned for MSTest and VS2017 Preview, updated https://youtrack.jetbrains.com/issue/RSRP-465541 request accordingly. – Alexander Kurakin Jul 25 '17 at 09:58
  • @AlexanderKurakin Excellent, well at least it's not something I'm doing ... Bummer, just saw your comment ... Happens in R# 2017.2 EAP builds as well – SteveC Jul 25 '17 at 10:52
  • 1
    Questions on SO should be phrased as questions :) – Matt Kerr Jul 31 '17 at 16:21
  • @MattKerr "As you wish" :-) – SteveC Aug 02 '17 at 14:41

2 Answers2

16

The answer, at least so far, is to install the R# 2017.2 EAP 13 ...

Yes, the 13, not the 12

SteveC
  • 15,808
  • 23
  • 102
  • 173
  • 3
    Here is a link to EAP13, since it doesn't appear on their official download list yet: http://download.jetbrains.com/resharper/JetBrains.ReSharperUltimate.2017.2.EAP13.exe – dlf Aug 21 '17 at 12:13
  • 1
    installing the latest using "Check for Updates" worked for me. Went from 2017.1.3 to 2017.2 built Aug 24 2017. – wonster Sep 11 '17 at 22:45
  • @wonser, I think you should consider moving your comment to an answer. That's what solved it for me. – ouflak Sep 30 '17 at 09:56
15

As of R# 2017.2 official build (Aug 24,2017), this should work again.

hcd
  • 1,338
  • 2
  • 10
  • 15