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

Missing classname when used with reports generated from VSTest.Console.exe

XMLWordPrintable

    • Icon: Patch Patch
    • Resolution: Unresolved
    • Icon: Major Major
    • mstest-plugin
    • None

      Visual Studio 2012 introduced VSTest.Console.exe to replace MSTest.exe.

      See here for more information:
      http://msdn.microsoft.com/en-us/library/vstudio/ms182486.aspx

      For the most part the trx output format is the same, except the class name is no longer in the full assembly reference format. It is now just the class name.

      MSTest.exe:
      className="Foo.AssemblyName.Namespace.TestClass, Foo.AssemblyName, Version=1.0.0.0, Culture=neutral, PublicKeyToken=0123abcd0123abcd"

      VSTest.Console.exe:
      className="Foo.AssemblyName.Namespace.TestClass"

      Attached is a modified xsl that addresses this difference. Please review and incorporate at your earliest convenience.

        1. mstest-to-junit.xsl
          4 kB

          [JENKINS-19360] Missing classname when used with reports generated from VSTest.Console.exe

          mrobinet created issue -

          mrobinet added a comment -

          mstest transform change

          mrobinet added a comment - mstest transform change
          mrobinet made changes -
          Attachment New: mstest-to-junit.xsl [ 24470 ]

          Glenn V added a comment -

          I would be happy if this got fixed, although the attached xsl is good enough to use as a workaround in combination with the "publish junit test result report" post build task.

          The "VsTestRunner plugin" does not publish unit test results properly either, so for now the only way to use vstest with jenkins is to script it yourself, it seems.

          Glenn V added a comment - I would be happy if this got fixed, although the attached xsl is good enough to use as a workaround in combination with the "publish junit test result report" post build task. The "VsTestRunner plugin" does not publish unit test results properly either, so for now the only way to use vstest with jenkins is to script it yourself, it seems.
          Glenn V made changes -
          Link New: This issue is related to JENKINS-21424 [ JENKINS-21424 ]

          Ivo Bellin Salarin added a comment -

          VSTestRunner plugin supports since 2014/08/31 the publishing of TRX files.

          Could you please integrate this XSL and tell us how to pass environment variables (like the ones described in https://github.com/jenkinsci/vstestrunner-plugin/pull/2) to the "Publish MSTest results report" task?

          Ivo Bellin Salarin added a comment - VSTestRunner plugin supports since 2014/08/31 the publishing of TRX files. Could you please integrate this XSL and tell us how to pass environment variables (like the ones described in https://github.com/jenkinsci/vstestrunner-plugin/pull/2 ) to the "Publish MSTest results report" task?

          SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Ivo Bellin Salarin
          Path:
          pom.xml
          src/main/resources/hudson/plugins/mstest/mstest-to-junit.xsl
          src/test/java/hudson/plugins/mstest/MSTestReportConverterTest.java
          src/test/resources/hudson/plugins/mstest/mstest_vs_2012.trx
          src/test/resources/hudson/plugins/mstest/mstest_vs_2012.xml
          http://jenkins-ci.org/commit/mstest-plugin/0f2aa07d0fa905819d21997b2595eec54c5fdc88
          Log:
          Merge pull request #3 from iansul/master

          JENKINS-19360 - Fix for mstest problems with trx files genereated by vstest.console.exe

          Compare: https://github.com/jenkinsci/mstest-plugin/compare/e11a4dc2471a...0f2aa07d0fa9

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Ivo Bellin Salarin Path: pom.xml src/main/resources/hudson/plugins/mstest/mstest-to-junit.xsl src/test/java/hudson/plugins/mstest/MSTestReportConverterTest.java src/test/resources/hudson/plugins/mstest/mstest_vs_2012.trx src/test/resources/hudson/plugins/mstest/mstest_vs_2012.xml http://jenkins-ci.org/commit/mstest-plugin/0f2aa07d0fa905819d21997b2595eec54c5fdc88 Log: Merge pull request #3 from iansul/master JENKINS-19360 - Fix for mstest problems with trx files genereated by vstest.console.exe Compare: https://github.com/jenkinsci/mstest-plugin/compare/e11a4dc2471a...0f2aa07d0fa9
          Ivo Bellin Salarin made changes -
          Assignee Original: acmarques [ acmarques ] New: Ivo Bellin Salarin [ nilleb ]
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

          s g added a comment -

          I'm facing same issue, but without any classname at all.

          Trx, generated by vstest: http://pastebin.com/bXKbZJZ5

          JUnitResult has empty <className></className>

          s g added a comment - I'm facing same issue, but without any classname at all. Trx, generated by vstest: http://pastebin.com/bXKbZJZ5 JUnitResult has empty <className></className>
          s g made changes -
          Resolution Original: Fixed [ 1 ]
          Status Original: Resolved [ 5 ] New: Reopened [ 4 ]

            nilleb Ivo Bellin Salarin
            mrobinet mrobinet
            Votes:
            8 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated: