nunit4teambuild Wiki & Documentation Rss Feed

Updated Wiki: sample script

MrKWatkins — Wed, 05 Aug 2009 18:57:53 GMT

This is a sample script that you can include in your build process. Note that the use of the <BuildStep> tasks are optional and you can remove those if you desire.

<Target Name="AfterCompile">

<BuildStep TeamFoundationServerUrl="$(TeamFoundationServerUrl)" BuildUri="$(BuildUri)" Name="NUnitTestStep" Message="Running Nunit Tests">
<Output TaskParameter="Id" PropertyName="NUnitStepId" />
</BuildStep>


<ItemGroup>
<TestAssemblies Include="$(OutDir)\**\cs-*.dll" />
</ItemGroup>


<NUnit ContinueOnError="true" Assemblies="@(TestAssemblies)" OutputXmlFile="$(OutDir)nunit_results.xml" ToolPath="$(ProgramFiles)\Nunit 2.4.7\bin\">
<Output TaskParameter="ExitCode" PropertyName="NUnitResult" />
</NUnit>
<BuildStep Condition="'$(NUnitResult)'=='0'" TeamFoundationServerUrl="$(TeamFoundationServerUrl)" BuildUri="$(BuildUri)" Id="$(NUnitStepId)" Status="Succeeded" />
<BuildStep Condition="'$(NUnitResult)'!='0'" TeamFoundationServerUrl="$(TeamFoundationServerUrl)" BuildUri="$(BuildUri)" Id="$(NUnitStepId)" Status="Failed" />


<Exec Command=""$(MSBuildProjectDirectory)\NUnitTFS.exe" -n "$(OutDir)nunit_results.xml" -t "$(TeamProject)" -b "$(BuildNumber)" -f "%(ConfigurationToBuild.FlavorToBuild)" -p "%(ConfigurationToBuild.PlatformToBuild)" -x "$(MSBuildProjectDirectory)\NUnitToMSTest.xslt"" />


<Error Condition="'$(NUnitResult)'!='0'" Text="Unit Tests Failed" />
</Target>

Updated Wiki: Home

MrKWatkins — Wed, 05 Aug 2009 18:56:19 GMT

Project Description
Add support for NUnit to TFS 2008's Team Build so that your NUnit test results are visible in the build log and incorporated into the data warehouse for reporting.

Great for teams with an existing investment in NUnit tests, or those who prefer NUnit over other testing frameworks.

To add support for NUnit to your build you need to follow a few simple steps:

Make sure NUnit is installed on your build server.
Unzip the files from the download and add them to source control in the same folder as your TFSBuild.proj
Update the NUnitTFS.exe.config file to point to your TFS server
Change your build script to run NUnit and then call the NUnitTFS utility (see the sample script for an idea of how this is done)
Run your build!

If it's all set up correctly the next time you build you should see your build logs looking something like this:

If you follow the sample script you'll also need to make sure you have the The MSBuild Community Tasks installed on your build server.

Version 1.0 required MSTest to be installed for publishing test results, but this is no longer a requirement as of version 1.1.

This release has been tested with NUnit 2.4.7, 2.4.8 and 2.5.

For more information see the developer notes and http://www.mrkwatkins.co.uk/Blog/2009/07/25/Making-NUnit-Play-Nicely-With-Team-Foundation-Server.

Updated Wiki: Home

rbanks54 — Fri, 31 Jul 2009 04:59:23 GMT

Make sure NUnit is installed on your build server.
Unzip the files from the download and add them to source control in the same folder as your TFSBuild.proj
Update the NUnitTFS.exe.config file to point to your TFS server
Change your build script to run NUnit and then call the NUnitTFS utility (see the sample script for an idea of how this is done)
Run your build!

If it's all set up correctly the next time you build you should see your build logs looking something like this:

If you follow the sample script you'll also need to make sure you have the The MSBuild Community Tasks installed on your build server.

Version 1.0 required MSTest to be installed for publishing test results, but this is no longer a requirement as of version 1.1.

This release has been tested with NUnit 2.4.7 and 2.4.8 and should work with NUnit 2.5 as well.

For more information see the developer notes and http://www.mrkwatkins.co.uk/Blog/2009/07/25/Making-NUnit-Play-Nicely-With-Team-Foundation-Server.

Updated Wiki: sample script

rbanks54 — Fri, 31 Jul 2009 04:40:52 GMT

This is a sample script that you can include in your build process. Note that the use of the <BuildStep> tasks are optional and you can remove those if you desire.

<Target Name="AfterCompile">

<BuildStep TeamFoundationServerUrl="$(TeamFoundationServerUrl)" BuildUri="$(BuildUri)" Name="NUnitTestStep" Message="Running Nunit Tests">
<Output TaskParameter="Id" PropertyName="NUnitStepId" />
</BuildStep>


<ItemGroup>
<TestAssemblies Include="$(OutDir)\**\cs-*.dll" />
</ItemGroup>


<NUnit ContinueOnError="true" Assemblies="@(TestAssemblies)" OutputXmlFile="$(OutDir)nunit_results.xml" ToolPath="$(ProgramFiles)\Nunit 2.4.7\bin\">
<Output TaskParameter="ExitCode" PropertyName="NUnitResult" />
</NUnit>
<BuildStep Condition="'$(NUnitResult)'=='0'" TeamFoundationServerUrl="$(TeamFoundationServerUrl)" BuildUri="$(BuildUri)" Id="$(NUnitStepId)" Status="Succeeded" />
<BuildStep Condition="'$(NUnitResult)'!='0'" TeamFoundationServerUrl="$(TeamFoundationServerUrl)" BuildUri="$(BuildUri)" Id="$(NUnitStepId)" Status="Failed" />


<Exec Command=""$(MSBuildProjectDirectory)\NUnitTFS.exe" -n "$(OutDir)nunit_results.xml" -t "$(TeamProject)" -b "$(BuildNumber)" -f "%(ConfigurationToBuild.FlavorToBuild)" -p "%(ConfigurationToBuild.PlatformToBuild)" -x "$(MSBuildProjectDirectory)\NUnitToMSTest.xslt"" />


<Error Condition="'$(NUnitResult)'!='0'" Text="Unit Tests Failed" />
</Target>

Updated Wiki: Home

rbanks54 — Fri, 31 Jul 2009 04:39:56 GMT

Run Nunit-console and produce an XML log file
Run the NUnitTFS utility to convert the NUnit results and publish them to the TFS Build Store

And then your build logs will look something like this:

Fortunately there is a sample script that you can include into your build. You then just need to obtain both the XSL Transform (see Releases) and make sure you have the following pre-requisites for your build server:

The MSBuild Community Tasks

As of Version 1.1, MSTest is no longer a requirement.

This release has been tested with NUnit 2.4.7 and 2.4.8

For more information see the developer notes and http://www.mrkwatkins.co.uk/Blog/2009/07/25/Making-NUnit-Play-Nicely-With-Team-Foundation-Server.

Updated Wiki: developer notes

rbanks54 — Wed, 25 Jun 2008 04:28:53 GMT

Some notes on the way the XSLT works.

First up, the format of NUnit results and MSTest TRX files are drastically different. There are some common items, but a TRX has repeated sections for tests (results summary & results) and the TRX files rely on GUIDs to cross reference results and executions.

Unfortunately generating GUIDs in a transform isn't possible and yet we need to generate the GUIDs for each transform as the TRX TestRun id GUID is used internally by TFS to uniquely identify test results. If we try publishing different test results using the same GUID then TFS will reject the second attempt with a message indicating the test results have already been published. What I've had to do is cheat and psuedo-generate the GUIDs based on date/time values extracted from the NUnit results.

In the XSLT this is done by the TestRunGUID template.

TRX's also use GUIDs internally for executionID's and testID's. These are generated from the test number. Basically I've used the NUnit test result number (from the $pos xsl variable), padded it with zero's and prepended a portion of a Guid onto it to form a properly constructed value. Since these only need to be unique within the test result file and not across test results (thankfully!) this is OK and makes it fairly easy to generate. Plus, because we're using the $pos xsl variable, it means we can generate the cross-referenced GUID values that the TRX needs without having to store the values. Phew!

The rest of the XSLT is a simple extract and transform operation. It's a bit lengthy because of the multiple passes of the NUnit results but it works :-).

Updated Wiki: Home

rbanks54 — Wed, 25 Jun 2008 04:10:21 GMT

Run Nunit-console and produce an XML log file
Convert the Nunit XML output to an MSTest test results file (with a .trx extension)
Use MSTest /publish to push merge the trx file with an existing build

The MSBuild Community Tasks
nxslt2 (a free command line .net XSLT utility)
MSTest needs to be installed on the build server

This release is tested with NUnit 2.4.7

For more information see: http://richardsbraindump.blogspot.com/2008/06/merging-nunit-build-results-into-tfs.html and the developer notes.