Test management warehouse: Improve deletion performance

Last week we received a complaint from an internal customer that the test management warehouse adapter is taking a lot of time to process the data. Dhruv took a look at the problem and found that it is slow because the indexes on the test management tables (FactTestResult, DimTestResult, DimTestRun) is highly fragmented. When he…

0

How to find test points assigned to a particular person

Here is a code snippet which you can use to find test points assigned to a particular person. # Load Client Assembly [Reflection.Assembly]::Load(“Microsoft.TeamFoundation.Client, Version=11.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a”); [Reflection.Assembly]::Load(“Microsoft.TeamFoundation.TestManagement.Client, Version=11.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a”); [Reflection.Assembly]::Load(“Microsoft.TeamFoundation.TestManagement.Common, Version=11.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a”);   # Define parameters $tfsCollectionUrl = “http://myserver:8080/tfs/DefaultCollection”; $projectName = "DefaultProject"; $planId = "1"; $userDisplayName = "Aseem Bansal"; # Connect to tfs…

0

Power-shell script to find test points for a particular suite/config

One of my customer is running into an issue while customizing his BDT workflow and to debug the issue, I have just now created a power-shell script which lists down the test points belonging to a particular suite/configuration. Since I have not seen any power-shell script on this till now (probably because of the issue…

0

How to enable Tfs job agent logs for lab operations

In this post, I want to talk about the steps which I typically perform to enable the job agent logs for lab operations. 1. Stop the TFS job agent service. (net stop tfsjobagent) 2.  Enable tracing for Tfs job agent. Take a backup of the tfsjobagent.exe.config file. (It is typically found under C:\Program Files\Microsoft Team…

0

How to enable lab agent logs

Here are the steps which I typically perform to enable lab agent logs. 1. Go to the lab agent installation directory (typically it is something like C:\Program Files\Microsoft Visual Studio Lab Management 10.0). 2. Open the configuration file named LabAgentService.exe.config and edit it as shown below. (Changed autoflush from false to true, removed comments from…

0

How to enable build agent or build controller’s logs?

Here are the steps which I typically perform to enable build agent/controller logs. 1. Go to the build agent/controller installation directory (typically it is something like C:\Program Files\Microsoft Team Foundation Server 2010\Tools). 2. Create a new configuration file named TFSBuildServiceHost.exe.config with the following content: <configuration>    <system.diagnostics>        <switches>            <add name=”BuildServiceTraceLevel” value=”4″/>        </switches>        <trace autoflush=”true” indentsize=”4″>            <listeners>               …

5

How to enable test agent logs

Here are the steps which you should perform to enable test agent logs. 1. Go to your test agent installation directory (typically it is something like C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\). 2. Open the agent service configuration file (QTAgentService.exe.config) and change the trace level to 4 and enable the trace listener as shown below:  …

6

Test run remains in “Waiting for test controller” state for ever

In this article, I wanted to share what you should do if you have queued an automated test run on a test controller and its remain in "waiting for test controller” state for quite some time (as shown below).  Before we go to the trouble shooting steps, let us spend sometime understanding what happens when…

14

How to enable test controller logs

Here are the steps which you should perform to enable test controller logs. 1. Go to your test controller installation directory (typically it is something like C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\). 2. Open the controller configuration file (QTController.exe.config) and change the trace level to 4 and enable the trace listener as shown below:   <system.diagnostics>   …

8