CODEWITHSUNDEEP
visual-studiounit-testingmsbuildtfsbuild
user3115698
user3115698

Reputation: 13

Error when running unit tests in automated build since VS upgrade to 2013 on TFS2012

I started creating automated builds in TFS 2012 using a build server with VS2012 on it. Everything was running fine, but then we updated the build server to VS2013(still with TFS 2012). Now no units execute. I get the error:

Handle Test Run Exception

Could not load file or assembly 'Microsoft.VisualStudio.TestPlatform.Utilities, 
Version=11.0.0.0, Culture=neutral, 
PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. 
The system cannot find the file specified.

I can find that file on the build server but only version 12 under vs2013.

Im lost as to what to do as I dont know what is forcing the Test Runner to use version 11 or how to change it.

Is it possible that since the build controller is tfs 2012, it is somehow forcing the Test Runner in the build to use version 11 instead of version 12 on the build server? Any ideas how to resolve this?

Upvotes: 1

Views: 3379

Answers (1)

allen
allen

Reputation: 4647

You need to have VS Professional or later on your build server to run automated tests as a part of your build process.

Here since TFS is still at 2012 the test activities are referring the 11.0 dlls and installing VS2012 should help resolve this issue.

This is a known bug being tracked.

From http://msdn.microsoft.com/en-us/library/ms253138.aspx

To run unit tests, or coded UI tests, you must install Visual Studio Professional or later

Upvotes: 3

Related Questions