Query for Test Results by Tester

TFS’s ITestCaseResultHelper interface (and its TFS API implementation, available via the ITestManagementTeamProject.TestResults property) provides a public API to find one particular ITestCaseResult (based on its TestRunId and TestResultId) and also allows you to perform a query against the TestResults, but unfortunately the later is quite under-documented and it is a bit unclear how to query for ITestCaseResults that were RunBy a particular user.

However, once you know it, it is in fact quite simple. What you need upfront is the Tester’s TeamFoundationIdentity (and obviously an existing ITestManagementTeamProject instance/connection) and based on that, you can do the following:

”[…]

ITestCaseResultCollection testCaseResultsByTester = testManagementTeamProject.TestResults.Query(string.Format(“select * from TestResult where RunBy = ‘{0}’”, teamFoundationIdentity.TeamFoundationId));

[…]”.

Conveniently, the ITestManagementTeamProject interface provides access to the ITfsIdentityStore via its corresponding .TfsIdentityStore property which allows you to retrieve the corresponding instance by its variety of Getter methods.

This works for both, TFS 2010 and 2012.

TFS2012: Hiding certain WorkItem Types from Users

If you’ve built a custom Process Template you might have added some WorkItem types that the user should not directly interact with (such as Microsoft’s Shared Step type), you can now (as of TFS 2012) hide these types by adding them to the corresponding Category entry, namely “Microsoft.HiddenCategory”.

Microsoft has added the following by default (unless you migrated, then you might want to add them by hand, too):

”[…]

<CATEGORY name=”Hidden Types Category” refname=”Microsoft.HiddenCategory”>

  <DEFAULTWORKITEMTYPE name=”Code Review Request” />

  <WORKITEMTYPE name=”Code Review Response” />

  <WORKITEMTYPE name=”Feedback Request” />

  <WORKITEMTYPE name=”Feedback Response” />

  <WORKITEMTYPE name=”Shared Steps” />

</CATEGORY>

[…]”

Source: msdn.microsoft.com

Standalone Team Foundation Server 2012 API (Client Object Model)

I just found out that Microsoft silently released the standalone version of their TFS 2012 API (called Client Object Model) a couple weeks back that allows creation of applications targeting a Team Foundation Server without the necessity of having a complete Visual Studio 2012 (Shell) installed on the target system, as normally required.

As redistribution of these bits was not allowed with the 2010 one (apparently for no practical but rather ‘legally unclear, hence not allowed’ reasons) and the 2012 one does not clearly state whether or not it is allowed now, I’ve inquired about this there, too.

Download Links:

Source: visualstudiogallery.msdn.microsoft.com

Extending Team Explorer in Visual Studio 2012 via ITeamExplorer* Interfaces

One of the improvements in Visual Studio 2012 is that it brings together the previously slightly scattered TFS functionality into the Team Explorer and even better, made extending the new Team Explorer a tad more convenient than it was before (it was doable, but rather cumbersome).

VS2012 has now a MEF based plugin model for its Team Explorer component and  Microsoft released an article accompanied by a code sample explaining & demonstrating implementation of the various interfaces (ITeamExplorerPage, ITeamExplorerSection, ITeamExplorerNavigationItem and ITeamExplorerNavigationLink, all within the Microsoft.TeamFoundation.Controls namespace) you can use to extended and add your own, custom functionality into the Team Explorer.

The article and code is available here, if you do need an expert that knows the TFS Client Object Model and Visual Studio Extensbility inside out, please don’t hesitate and contact me. 

Source: code.msdn.microsoft.com