Can not run tests on build server
I get this error on the build server:
MSBUILD : warning : Failed to instantiate type 'Microsoft.VisualStudio.TestTools.WebStress.WebTestRunConfig, Microsoft.VisualStudio.QualityTools.LoadTest, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a': Could not load file or assembly 'Microsoft.VisualStudio.QualityTools.LoadTest' or one of its dependencies. The system cannot find the file specified.
Whats missing?
/Chris
You need to install VS 2005 Testing Tools on the server. That is you need Team Suite, Tester edition, and run the installation on the server. But you only need to select testing tools.
If you clients only run the Developer Edtion, you can also install the Testing Tools form the Team Developer Edtion on the server. But if just one of your clients runs e.g. the Team Suite Trial Edtion, that person, is not allowed to touch the .vsmdi file. If he does you will get the same error, because the Load Testing assemblies will be referenced.
Now... I don't know whether this requires a license on the server, or whether you can use the Team Suite Trial Edtion to install the needed assemblies, on the server. Microsoft?
I mean neither of these products are cheep, so I really don't hope I need to buy a license, for each build server I'm planing to install. But if they are in fact free, why are the not installed with the Build Server? Microsoft?
Honestly, I think this is realy bad choice by Microsoft. And it is not even documentet very well.
Thomas
Turns out it is the localtestrun.testrunconfig that references the assemblies. I removed it and let VS recreate it and no more problems for me.
Thanks for the pointers though.
Thomas,
See http://www.microsoft.com/downloads/details.aspx?familyid=1FA86E00-F0A3-4290-9DA9-6E0378A3A3C5&displaylang=en for a whitepaper on Team System licensing. From the whitepaper:
"As part of the build process, Team Foundation Server may run quality tests and/or analysis on the precompiled or compiled code. These tests rely on functionality found within Team System client products, typically within the Team Edition for Software Developers or Team Edition for Software Testers products. These products may be installed on the build machine by licensed users of those products, as long as they are not directly used by any individuals who are not licensed for those products."
Hope this is helpful.
Hi Aaron
Thanks for you answer.
But this is not good enough.
E.g. I have Team System Suite Trial Edition installed. My company only has a Developer Edition License. When I edit the vsmdi file using my Team Suite, the file is changed in a way that I get the error, which started this thread.
I'm not using any of the Team Suite tools, I just happened to install the Team Suite Trial, the day that VS 2005 was released.
In a fully licensed scenario, I can see the same problem. E.g. i know that MVP's has the Team Suite (as a personal License... not a company license). If one of those was employed in my company, I would make a policy saying that nobody is allowed to used the Team Suite Edition, because we risk them breaking the daily build if they tuch the vsmid file.
Se my point?
In my opinion the Team Suite Testing tools should be part of the Team Foundation Build Server. Or I should be allowed to install the Testing Tools from the Trial Edition.
Thomas
