Unit Tests not running with DotCover, VS 2017 and MSTest 2.0

Completed

When I try to cover unit tests with DotCover in a VS 2017 project using MSTest 2.0, all the tests are inconclusive with "Test not run". In the log (within the test sessions window), it says "Coverage analysis: Instrumentation was requested, but wasn't made", followed by "Element {test name} was left pending after its run completion" for every unit test. Running them without coverage works fine.

A VS 2015 project using MSTest 2.0 has no issues, and a VS 2017 project using MSTest 1.0 has no issues.

I've tried collecting logs, but I don't know what I'm looking for; there appear to be logs for "Build", "Install" and "JetBrains", but I can't see anything in them that appears testing related.

7 comments

Hello Shawn,

Which dotCover version are you using? If it's 2016.3 or older than this is a known issue. We have added support for MSTest v2 to dotCover 2017.1. You are welcome to try the latest EAP: https://www.jetbrains.com/resharper/eap/

Best regards.

0

I was using 2016.3.2. I updated to the EAP version and it seems to be working fine. Thanks!

0

I am having a similar issue, all my tests are showing as "Inconclusive: Test not run" in Continuous Testing Sessions but the same tests run just fine under Unit Test Sessions.  There is 1 error listed that reads "Coverage analysis: Can't start analysis. Operation was canceled by user.  Failed to verify x64 COM object registration: Empty path to COM object."

I am using dotCover 2017.2 (downloaded and installed less that 3 weeks ago).

0

Hello Scott,

There could be several reasons for this error:
- Unfinished Windows updates. Could you please try to reboot your machine, install all updates for Windows and check if the issue persists?
- One more possible reason is a limited user account. The error message means that HKEY_CURRENT_USER\SOFTWARE\Classes was not mapped to HKEY_CLASSES_ROOT. It is the part of OS protection which is active for some accounts in OS. Do you indeed use some limited account?

0

Fedor,

I do run under a limited access account, unfortunately it's not something I can change. The error that I saw, the one in my original post, seems to have gone away but I have seen the behavior twice since posting...the log always read "OK" for those so it's hard to know what caused it.  However, the project(s) in question has several web.config transforms and I was able to get things going again after cleaning and rebuilding the solution under a different config.  I think one of those may have been the culprit but I have not been able to reproduce the issue again since so I'm not sure which web.config caused the issue or why.

0

Hello Scott

Thanks a lot for the details! Glad to hear that it works fine now.

0

have the same problem here.  Not a limited account.  What can I provide to you to help out?

1

Please sign in to leave a comment.