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 !

6
  • 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) - youtrack.jetbrains.com/issue/RSRP-464754. Try installing R# 2017.2 EAP build jetbrains.com/resharper/eap Commented Jul 25, 2017 at 8:54
  • @AlexanderKurakin Nope not using any .NET Core Commented Jul 25, 2017 at 8:56
  • 2
    Just reproduced the issue you'd mentioned for MSTest and VS2017 Preview, updated youtrack.jetbrains.com/issue/RSRP-465541 request accordingly. Commented Jul 25, 2017 at 9: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 Commented Jul 25, 2017 at 10:52
  • 1
    Questions on SO should be phrased as questions :) Commented Jul 31, 2017 at 16:21

2 Answers 2

16

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

Yes, the 13, not the 12

Sign up to request clarification or add additional context in comments.

3 Comments

Here is a link to EAP13, since it doesn't appear on their official download list yet: download.jetbrains.com/resharper/…
installing the latest using "Check for Updates" worked for me. Went from 2017.1.3 to 2017.2 built Aug 24 2017.
@wonser, I think you should consider moving your comment to an answer. That's what solved it for me.
15

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

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.