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

Version 1.0.5 fails to test unit test assemblies specified with a relative path

    Details

    • Similar Issues:

      Description

      Some time ago, we upgraded the VSTestRunner plugin from version 1.0.4 to 1.0.5. From that time on, all of my .Net projects builds failed in the build step associated with that plug-in.

      The error message was:

      Path To VSTest.console.exe: …\vstest.console.exe
      no file matches the pattern ".\Sources\…\bin\Release\….dll"
      ".\Sources\…\bin\Release\….dll"Build step 'Run unit tests with VSTest.console' marked build as failure

      (Replaced some parts of paths with ellipses)

      When I had reverted to the 1.0.4 version, the build step were once again executed succesfully.

       

        Attachments

          Activity

          rschreurs R. Schreurs created issue -
          Hide
          dwright Debbie Wright added a comment -

          this appears to still be an issue in 1.0.7, unable to use the plugin at all.

          Show
          dwright Debbie Wright added a comment - this appears to still be an issue in 1.0.7, unable to use the plugin at all.
          Hide
          test12345678910 Test Test added a comment - - edited

          Debbie Wright I can confirm that, too. Seeing the exact same issue with version 1.0.7. We are using Jenkins 2.138.2.

          Show
          test12345678910 Test Test added a comment - - edited Debbie Wright I can confirm that, too. Seeing the exact same issue with version 1.0.7. We are using Jenkins  2.138.2.
          Hide
          mayank Mayank Parmar added a comment -

          I can confirm that, too. Seeing the exact same issue with version 1.0.8. We are using Jenkins 2.176.2. [At this moment both are latest]

          Show
          mayank Mayank Parmar added a comment - I can confirm that, too. Seeing the exact same issue with version 1.0.8. We are using Jenkins 2.176.2. [At this moment both are latest]
          mayank Mayank Parmar made changes -
          Field Original Value New Value
          Rank Ranked higher
          mayank Mayank Parmar made changes -
          Priority Minor [ 4 ] Blocker [ 1 ]
          Hide
          mayank Mayank Parmar added a comment -

          There is a workaround for this and it would be to Execute Windows Batch Command with parameters similar to:

          "C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow\vstest.console.exe" TestFolder\bin\x86\Release\Test.dll

           ** I was able to append /Logger:trx to the command line and use the Post Build Publish MS test result to create a report.

          Show
          mayank Mayank Parmar added a comment - There is a workaround for this and it would be to  Execute Windows Batch Command  with parameters similar to: "C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow\vstest.console.exe" TestFolder\bin\x86\Release\Test.dll  ** I was able to append /Logger:trx to the command line and use the Post Build Publish MS test result to create a report.

            People

            • Assignee:
              Unassigned
              Reporter:
              rschreurs R. Schreurs
            • Votes:
              2 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated: