Category: visual studio test
David Naveen on Thu, 26 May 2016 12:25:52
Can you please help me with that? It would be a great help. Thank you in advance.
Weiwei Cai on Fri, 27 May 2016 02:43:26
Please check your Visual Studio 2010 Ultimate first, whether it has installed the SP1. According to the part of Support matrix from MSDN in TFS 2013 compatibility and dependencies, the Visual Studio 2010 SP1 is required if you are using TFS 2013.
Then please run your Test on the build machine with MSTest.exe to check whether it also has this issue. If it works fine in the build machine, the problem should be related to TFS configurations. I will involve TFS experts to help us find out what happened with your TFS configurations.
If it has the same problem in build machine, please tell us which version of Test Controller and Test Agent you are using and what type of test project (Unit Test, Coded UI Test or others) you are running. I will create a sample project based on your test environment try reproduce the problem.
David Naveen on Fri, 27 May 2016 05:06:45
Hi Weiwei Cai,
Sorry for the mistake in my previous post. I have installed VS2013 Ultimate in my controller machine.
The Test Controller is configure with Load Testing (Not using Team Project Collection).
I have used Microsoft Agents for Visual Studio 2013 Version:12.0.40629.0 Update 5 for Test Controller and Test Agent machine.
Weiwei Cai on Sat, 28 May 2016 09:10:11
Thanks for your response.
According to your second post, you are running your Load Test using Test Controller and Test Agent on a remote machine without TFS, is it right?
Please try with following steps to set Test Controller and Test Agent log level to check this problem occurs on Controller side or Agent side and whether there has any detailed information for this issue.
Set Controller Log:
- Stop the test controller service. At a command prompt, type net stop vsttcontroller.
- Open the file QTController.exe.config. This file is located in the controller installation directory.
- Edit the entry for the EqtTraceLevel switch in the system diagnostics section of the file. Your code should resemble as below. Then save the file and Start the controller service. At a command prompt, type net start vsttcontroller.
<system.diagnostics> <trace autoflush="true" indentsize="4"> <listeners> <add name="myListener" type="System.Diagnostics.TextWriterTraceListener" initializeData="d:\VSTestHost.log" /> </listeners> </trace> <switches> <!-- You must use integral values for "value": 0 = off, 1 = error, 2 = warn, 3 = info, 4 = verbose. --> <add name="EqtTraceLevel" value="4" /> </switches> </system.diagnostics>
Set Agent Log:
- Go to your test agent installation directory (typically it is something like
C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\).
- Open the agent service configuration file (QTAgentService.exe.config) and change
the trace level to 4 and enable the trace listener as shown below:
<system.diagnostics> <switches> <!– You must use integral values for “value”. Use 0 for off, 1 for error, 2 for warn, 3 for info, and 4 for verbose. –> <add name=”EqtTraceLevel” value=”4″ /> </switches> </system.diagnostics> ….. <add key=”CreateTraceListener” value=”yes”/> </appSettings> </configuration>
3. Do step 2 for agent execution processes (QTAgent.exe.config,
QTAgent32.exe.config) and agent collection processes (QTDCAgent.exe.config and
4. Restart the test agent (service or process).