Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Incomplete
-
None
-
Jenkins 1.614
MSTest Plugin 0.18
VSTest Runner plugin 1.0.4
Description
MSTest Plugin reports the following error after a successful build with MSBuild and test run with VSTest Runner. The mentioned file TestResults\vstest.coveragexml exists (I generate it with "C:\Program Files (x86)\Microsoft Visual Studio 12.0\Team Tools\Dynamic Code Coverage Tools\CodeCoverage.exe" analyze /output:"%WORKSPACE%\TestResults\vstest.coveragexml" "%VSTEST_RESULT_COVERAGE%"
MSTest: Processing tests results in file(s) E:\jenkins\data\jobs\ProjectX\workspace\TestResults\jenkins_ARIEL 2015-05-21 10_16_33.trx MSTest: E:\jenkins\data\jobs\ProjectX\workspace\TestResults\jenkins_ARIEL 2015-05-21 10_16_33.trx [MSTEST] XML coverage report file not found: E:\jenkins\data\jobs\ProjectX\workspace\TestResults\vstest.coveragexml [MSTEST] XML coverage report file not found: E:\jenkins\data\jobs\ProjectX\workspace\TestResults\jenkins_ARIEL 2015-05-21 10_16_33.coveragexml
Thanks for your feedback, Daniel.
I am sorry, the mstest-plugin message you point out is slightly wrong. It should state something different:
[MSTEST] XML coverage report file not found or its format is not supported [..]
The problem you experience is due to the fact that .coveragexml files content may differ according to the tool which has produced them. The mstest-plugin reads the format produced by Visual Studio (or by an handmade tool written according to the instructions gave on MSDN). SonarQube reads the format produced by CodeCoverage.exe uniquely. Visual Studio is able to read both formats.
I hope to have the time to produce an XSLT which converts the CodeCoverage.exe format to the format produced by Visual Studio. Until then, I suggest you to use a different tool to produce the .coveragexml file..
I have updated the wiki for the MSTest-plugin according to the above text. It could take a while before the wiki changes get published.