Not everyone have embraced Microsofts testing platform, but prefer to use other tools for unit testing, for instance NUnit. Because this is such a common scenario there is lots of information and components to help with integrating NUnit in Team Foundation Build.
The easiest solution is to use two add-on components. MSBuild Community Tasks to make configuration easier and NUnit for Team Build to integrate the testresults in the build log and get the results in reports. Both of these components are open source and free to download.
Begin with installing NUnit, MSBuild Community Tasks and NUnit for Team Build. After that only some changes in TFSBuild.proj are needet to get a really nice integration of NUnit in Team Foundation Server.
Import MSBuild Community Tasks by adding the following row:
Now we have the possibility to use every task that is defined in the imported file, but the one we are interested in here is only the one that concerns NUnit. To add an NUnit task, add the following at the bottom of TFSBuild.proj:
If you would like to run the test with a specific App.config like a testrunconfig file, it is possible to put the App.config file in the Source Control tree in the same directory as TFSBuild.proj. By running a copy command in the test task the special App.config could be copied with the current build. Add the following row for the concerned test DLL:s before the NUnit step:
Note the /y attribute which means that an existing file will be overwritten automatically.
The easiest solution is to use two add-on components. MSBuild Community Tasks to make configuration easier and NUnit for Team Build to integrate the testresults in the build log and get the results in reports. Both of these components are open source and free to download.
Begin with installing NUnit, MSBuild Community Tasks and NUnit for Team Build. After that only some changes in TFSBuild.proj are needet to get a really nice integration of NUnit in Team Foundation Server.
Import MSBuild Community Tasks by adding the following row:
<Import Project="$(MSBuildExtensionsPath)\MSBuildCommunityTasks\MSBuild.Community.Tasks.targets" />
Now we have the possibility to use every task that is defined in the imported file, but the one we are interested in here is only the one that concerns NUnit. To add an NUnit task, add the following at the bottom of TFSBuild.proj:
<Target Name="AfterCompile">
<!-- Create a Custom Build Step -->
<BuildStep TeamFoundationServerUrl="$(TeamFoundationServerUrl)" BuildUri="$(BuildUri)" Name="NUnitTestStep" Message="Running Nunit Tests">
<Output TaskParameter="Id" PropertyName="NUnitStepId" />
</BuildStep>
<!-- Get Assemblies to test -->
<ItemGroup>
<TestAssemblies Include="$(OutDir)\**\cs-*.dll" />
</ItemGroup>
<!-- Run NUnit and check the result -->
<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" />
<!-- Regardless of NUnit success/failure upload the results to TFS. -->
<Exec Command=""$(MSBuildProjectDirectory)\NUnitTFS.exe" -n "$(OutDir)nunit_results.xml" -t "$(TeamProject)" -b "$(BuildNumber)" -f "%(ConfigurationToBuild.FlavorToBuild)" -p "%(ConfigurationToBuild.PlatformToBuild)" -x "$(MSBuildProjectDirectory)\NUnitToMSTest.xslt"" />
<!-- If NUnit failed it's time to error out -->
<Error Condition="'$(NUnitResult)'!='0'" Text="Unit Tests Failed" />
</Target>
If you would like to run the test with a specific App.config like a testrunconfig file, it is possible to put the App.config file in the Source Control tree in the same directory as TFSBuild.proj. By running a copy command in the test task the special App.config could be copied with the current build. Add the following row for the concerned test DLL:s before the NUnit step:
<Exec Command="copy "$(MSBuildProjectDirectory)\App.config" "$(OutDir)\MyTest.dll.config" /y" />
Note the /y attribute which means that an existing file will be overwritten automatically.
Comments
Post a Comment