Test Scribe for MTM 11 Beta is out

  The Test Scribe Power Tool, which is used to generate documentation for test plan and test run for Microsoft Test Manager (MTM) has been updated for MTM 11 Beta.  The updated version is here.  The MTM 2010 version continues to be here.

0

MTM’s compatibility with TFS

Microsoft Test Manager (MTM) is forward and backward compatible with TFS.  This mean you can use – MTM 2010 with TFS 11.  To do so, you need to install the Compatibility GDR. MTM 11 with TFS 2010.  This is supported without any extra install. Since many new features require change in both the client and…

0

How To: Get the TFS AT log

In my previous post, I mentioned how to get the client side logs for Microsoft Test Manager (MTM) for reporting any issues.  In some cases, the client side logs are not enough and to figure out the issues we might need the Team Foundation Server (TFS) logs too.  On server, we have various logging mechanism…

1

Test Attachment Cleaner power tool released!!!

We have released new power tool called Test Attachment Cleaner that can be used to delete unwanted attachments test attachments from the TFS. For more details, refer here.

0

Continuous Integration with Assembly Version task

Changgyu from Avanade brought this interesting problem to my attention – If you are using Continuous Integration with Assembly Version task, build server will go into infinite recursion of builds.  Each CI build will update the assembly version and the task will make the checkin, which in turn will ask the CI web service for another build….

2

Passing custom properties to each individual solutions in Team Build

Though one of my earlier blogs is titled “Building .NET 1.1 application using Team Build”, the principal used in that blog can easily be generalized to pass any custom property to each solution/project file while building using Team Build. Say you want to sign each assembly built by a key. One option is to open each…

2

Writing a custom MSBuild Logger for Team Build

While building using Team Build, the build process creates one log file (for compilation and code analysis errors and warnings) per platform-flavor for all solutions.  However, few weeks back, while talking to a customer about Team Build, a new requirement came up. The customer wanted to have one log file per platform-flavor per solution. In his scenario, they had not…

2

Building .NET 1.1 application using Team Build

One of the FAQs in Team Foundation forums have been on “how to build .NET 1.1 application using Team Build”.   My colleague Nagaraju put up this blog to give out detailed steps for this. Apart from this, there were various other solutions on how to build .NET 1.1 using MSBuild (and hence in turn by Team…

7

Using AssemblyInfo task with Team Build

Fixed a bug in the snippet as pointed out by Peter from Microsoft Consulting Service. I was earlier using ItemGroup to get all AssemblyInfoFiles which gets executed before any target (and hence before Get task). So, the items in AssemblyInfoFiles may be outdated. The right approach is to use CreateItem task inside AfterGet target. Neil Enns…

4

Who requested this build?

In certain scenarios you may want to take different actions based on user who have requested the build (or may simply want to report that in log file).  Though the Team Build stores the name of the user who has requested the build (and this is shown in the UI), the value is not passed to…

0