Why does Resharper 9 intermittently fail to detect all my tests?

I recently updated to Resharper 9 and use Visual Studio 2013. I've tried all the obvious fixes of:

  • Cleaning and rebuilding solution, restarting Visual Studio, etc
  • Checking that my Resharper general settings match those of other people in the company who are not having this issue
  • Cleaned my Resharper cache and restarting Visual Studio
  • Uninstalling and reinstalling Resharper
  • Manually setting the processor architecture in both Visual Studio and Resharper


None of these have had any effect, except that occasionally toggling my processor architecture to the wrong one for the project and then rebuilding will suddenly make the tests detectable for the day. Any ideas on the reason for this?

8 comments
Comment actions Permalink

Hello Alla,

  Please try installing ReSharper 9.1 EAP https://confluence.jetbrains.com/display/ReSharper/ReSharper+9.1+EAP. We have fixed some related issues there.

Thanks!

0
Comment actions Permalink

Hi Alexander,

I installed 9.1 EAP 03, but I'm still having the same issue.

0
Comment actions Permalink

This seems to be a bug that was introduced in r#9 since r#8. It was a really big issue in 9.0, it significantly improved with 9.0.1. It "feels" like it is no longer than an issue to me, but it still may have happened once or twice.

Are you seeing it consistently/regularly?

The fact 9.1 EAP was mentioned clearly it's still recognized as an incomplete fix

0
Comment actions Permalink

Yeah, I may have to downgrade a version. It happens to me very regularly, nearly every day.

0
Comment actions Permalink

Hello Alla,

  Thanks for the reply.

  What Unit Test Framework do you use - MSTest or NUnit?

Thanks!

0
Comment actions Permalink

No worries - NUnit.

0
Comment actions Permalink

Hello Alla,

  Are you able to reproduce the issue in a sample demo solution? I was not able to reproduce the same behavior and we've fixed the related issue in R# 9.1 EAP https://youtrack.jetbrains.com/issue/RSRP-429003.

Thanks!

0
Comment actions Permalink

I'm having a lot of trouble replicating the error with a small solution - it seems to only happen for very big projects that my company works on, while none of my personal projects have this issue and I can't seem to trigger it by adding similar tests and dependencies to a clean project. Is there any way that could be related to the problem?

0

Please sign in to leave a comment.