Viewing test results in a web browser

Rido posted a cool way to see your test results from a build without having to copy the information locally and view it in VS.  Pretty cool!

TestResults Reports in TFS Builds

If you use TFSBuilds with VS UnitTests, you know how to inspect the TestResults: you must download the whole directory to your local machine, and sometimes this folder could be pretty huge.

So, if you want to check the error details of your tests, you can use my tool trx2html to convert the *.trx files to html, so you can see the reports with any browser.

Here are the instructions in 3 simple steps:

1) copy the RidoTasks.dll file to your source tree


2) Reference the msbuild task in TFSBuild.proj

<UsingTask TaskName="RidoTasks.trx2html" AssemblyFile="$(SolutionRoot)\GEN4\tools\RidoTasks.dll" />

3) Convert the test reports after drop the build results

<Target Name="AfterDropBuild">

    <CallTarget Targets="CreateTRXReports" />


<Target Name="CreateTRXReports">

   <CreateItem Include="$(DropLocation)\$(BuildNumber)\TestResults\*.trx">

  <Output TaskParameter="Include" ItemName="trxfiles"/>


<RidoTasks.trx2html FileName="%(trxfiles.Identity)" />


tags: , , , , , ,

Comments (3)

  1. Mike says:


    Is the .TRX file format an open and stable format. ie is it detailed somewhere, and is it sensible to code tools against it.  Is it likely to change drastically between versions?

    I am considering writing a converter for Clover.NET coverage output to .TRX so that I can import the results into TFS.  thoughts?



  2. buckh says:

    I asked, and here’s the response that I got.

    "In Orcas it will be open and relatively stable.  It is now in an XML schema.

    I wouldn’t say it won’t change, but we’ll update the XML schema version."

    So, you can do it, but you’ll have to potentially update it quite a bit when Orcas ships.


  3. Leon says:

    The XML schema in VS2008/Orcas changed. The  trx2html crashes when it is transforming a TRX to HTML.

Skip to main content