19

Test which use Microsoft Fakes Framework fail with exception: Microsoft.QualityTools.Testing.Fakes.UnitTestIsolation.UnitTestIsolationException: Failed to resolve profiler path from COR_PROFILER_PATH and COR_PROFILER environment variables

VS solution and builds were originally created in VS 2012 and run fine under TFS 2012 build/ controller, but not under TFS 2013. I do have Ultimate VS 2012 and Ultimate VS 2013 installed on TFS 2013 build server. While troubleshooting this issue, I changed test setting in the build definition from using "Visual Studio Test Runner" to "MSTest.exe Test Runner (VS 2010 Compatible)", and now not able to change it back as "Visual Studio Test Runner" is no longer an option in the drop-down of choices. I even replaced build template in TFS 2013 with the one in TFS 2012 but "Visual Studio Test Runner" is still not an option in the drop-down of choices in the build definition Process\Automated Tests section while editing Test Run.

How to solve the problem and get the tests which use Microsoft Fakes to run in TFS 2013 build?

user3665347
  • 191
  • 1
  • 5

2 Answers2

3

I was having this exact same problem and it turned out that I had a .testsettings file created in my solution and was telling the test runner in the IDE to use it. If you are getting this error in the Visual Studio IDE, verify that you do not have a .testsettings file specified by going under the Test menu -- if there is a .testsettings file specified with a checkmark next to it, click it to remove the checkmark. I suspect the presence of the .testsettings file causes Visual Studio to initialize the test runner differently.

enter image description here

If this is happening on the build server, verify that your build definition does not have a .testsettings file specified; ideally, perhaps remove the file altogether from source control and/or your solution. The presence of this file can trip up a TFS build.

codechurn
  • 3,870
  • 4
  • 45
  • 65
  • Fakes are working under VSTest.Console, not "legacy" MSTest. To force Visual Studio to invoke VSTest you need to remove .testsettings file. See more about differences between VSTest and MSTest in my blog https://wordpress.com/post/mfreidge.wordpress.com/172797 – Michael Freidgeim May 01 '16 at 10:08
  • 1
    It worked for me after unselecting the ".testsettings" and reopening the solution on Visual Studio. – Samir Sep 27 '16 at 04:16
1

I got the exact same error, but in my case it was a bug in ReSharper 2017.3.1: https://youtrack.jetbrains.com/issue/RSRP-467796

Already fixed in ReSharper 2018.1

itsho
  • 4,640
  • 3
  • 46
  • 68