[UPDATED, see this]
I have created a task that runs some unit tests in a certain DLL and the publish the result to a TFS service. We use this task in our TFS MSBuild script in order to execute some integration tests in the last step of the build process. In order to get some value from the integration tests the solution needs to be deployed, for example.
The most tricky parts of figuring this out was:
- The path to MSTest.exe - as it turns out there are a environment variable to the root of the Visual Studio Tools - %VS90COMNTOOLS%. And via that we can reach MSTest.exe with %VS90COMNTOOLS%\..\IDE\MSTest.exe
- To publish a build you need the buildId to send to the publishbuild-parameter of MSTest. It can easily be obtained from the TFSBuild parameter $(BuildNumber)
So here you are - my task to run tests and publish the results:
<!– Run integrationtests –> <Target Name=”RunIntegrationTests” Condition=”’$(DeployPT)’ == ‘true’”> <!– Write nice message to log and in the build progress –> <BuildStep TeamFoundationServerUrl=”$(TeamFoundationServerUrl)” BuildUri=”$(BuildUri)” Name=”Integrationstester” Message=”$(PROMPT) Kör integrationstester mot den publicerade PT” Status=”Succeeded” /> <Message Text=”$(PROMPT) Kör integrationstester mot den publicerade PT” />
<!– Vi kör testerna med ett dos-kommando mot MSTest eftersom vi vill köra det här i processen och inte i det normala test-flödet för TFSBuild. –>
<Exec Command=”"%VS90COMNTOOLS%\..\IDE\MSTest.exe" /testcontainer:$(BinariesRoot)\Debug\Test.Integration.dll /publish:server.url /publishbuild:$(BuildNumber) /flavor:debug /platform:AnyCPU /teamproject:MyProject” ContinueOnError=”false” />
</Target>