Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-28517

[MSTEST] XML coverage report file not found

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Minor
    • Resolution: Incomplete
    • mstest-plugin
    • 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
      

      Attachments

        Activity

          You could find useful the documentation produced by an anonymous user (on the wiki):
          https://wiki.jenkins-ci.org/display/JENKINS/MSTest+Plugin

          I've also started to work on a couple of XSL transforms to convert back and forth to the VisualStudio/CodeCoverage.exe format. They're available in the github repository : https://github.com/jenkinsci/mstest-plugin/tree/master/src/main/resources/hudson/plugins/mstest

          nilleb Ivo Bellin Salarin added a comment - You could find useful the documentation produced by an anonymous user (on the wiki): https://wiki.jenkins-ci.org/display/JENKINS/MSTest+Plugin I've also started to work on a couple of XSL transforms to convert back and forth to the VisualStudio/CodeCoverage.exe format. They're available in the github repository : https://github.com/jenkinsci/mstest-plugin/tree/master/src/main/resources/hudson/plugins/mstest
          kwaxi Daniel Wagner added a comment -

          I've to finish my sample project to create sample data but didn't find the time yet.

          kwaxi Daniel Wagner added a comment - I've to finish my sample project to create sample data but didn't find the time yet.

          Any news?

          nilleb Ivo Bellin Salarin added a comment - Any news?

          Could you please add some details about what's going wrong with the yasu-s coverage converter?
          Could you please provide the coveragexml files you get, if any?

          nilleb Ivo Bellin Salarin added a comment - Could you please add some details about what's going wrong with the yasu-s coverage converter? Could you please provide the coveragexml files you get, if any?
          kwaxi Daniel Wagner added a comment -

          Conversion with https://github.com/yasu-s/CoverageConverter doesn't solve the problem. I'll give you an update when I tried the other approach.

          kwaxi Daniel Wagner added a comment - Conversion with https://github.com/yasu-s/CoverageConverter doesn't solve the problem. I'll give you an update when I tried the other approach.

          Please read the release notes for the 0.14 version on the wiki page.

          https://wiki.jenkins-ci.org/display/JENKINS/MSTest+Plugin

          nilleb Ivo Bellin Salarin added a comment - Please read the release notes for the 0.14 version on the wiki page. https://wiki.jenkins-ci.org/display/JENKINS/MSTest+Plugin
          kwaxi Daniel Wagner added a comment -

          Do you have any suggestion which tool to use for generation of the .coveragexml?

          kwaxi Daniel Wagner added a comment - Do you have any suggestion which tool to use for generation of the .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.

          nilleb Ivo Bellin Salarin added a comment - 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.

          People

            nilleb Ivo Bellin Salarin
            kwaxi Daniel Wagner
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: