So, our TFS 2013 builders are doing everything right, except for reporting code coverage. I saw similar questions here, for example. TFS 2013 - there are no code coverage results , but we have already tried the proposed fixes without any results.
UPDATE 1 - we have taken more steps to try and resolve this; here is the full list:
- Verify that Visual Studio Ultimate was installed on the build server
- I tried setting the assembly definition of "CodeCoverageEnabled" to true, as well as the option "Code coverage is enabled"
- Verify that the assembly used the Debug configuration and that PDBs were created for the tested DLLs.
- Added .runsettings file with the correct ModulePath module included under <CodeCoverage> (it was checked in the build log that the path to the module was interpreted correctly, it would lead to errors if we intentionally distorted it)
- Registered .runsettings file
- Set the assembly definition to "Custom" and point to the .runsettings file
The build process itself works great. We can get code coverage results when we build a project locally in the IDE. On the build server, both the MSTest and NUnit test projects work fine, and we see that the results of the skip / crash are expected. The "No Code Coverage Results" message still covers us.
Update 2 -
Here's what we see in the execution log:
- qaru.site/questions/485225/..., 150 TFS 2013 VS Ultimate 2013 MSDN .