-
Bug
-
Resolution: Unresolved
-
Blocker
-
Jenkins 2.73.2
VSTestRunner plugin 1.0.5
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.
[JENKINS-49343] Version 1.0.5 fails to test unit test assemblies specified with a relative path
dwright I can confirm that, too. Seeing the exact same issue with version 1.0.7. We are using Jenkins 2.138.2.
Test Test
added a comment - - edited dwright I can confirm that, too. Seeing the exact same issue with version 1.0.7. We are using Jenkins 2.138.2. 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]
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.
Is this issue fixed?
I thought of using workaround but how to we create logger.trx and use the post-build publish to create a report, can someone guild me
sharath Kumar
added a comment - - edited Is this issue fixed?
I thought of using workaround but how to we create logger.trx and use the post-build publish to create a report, can someone guild me
Amit Dar
added a comment - I'm using the plugin version 1.0.8 and Jenkins 2.249.2, issue still exists.
I believe it is not going to be fixed in the foreseeable future....
Amit Dar
added a comment - I'm using the plugin version 1.0.8 and Jenkins 2.249.2, issue still exists.
I believe it is not going to be fixed in the foreseeable future.... 
chuang shao
added a comment - I read source code , found that: with the VSTestRunner plugin, the way to find test dll files is different.
Use the testfiles parameter directly, the Jenkins plug-in will convert the path to the real path.
It does not support the transmission of wildcard parameters.
It will call getTestFilesArguments function to obtain the full path of the file. Use the'**
*tests.dll' parameter, and getTestFilesArguments function will return no files matching.
You could try to use cmdLineArgs like :
vsTest settings: "testexecute.runsettings", cmdLineArgs: "**
*tests.dll"
chuang shao
added a comment - I read source code , found that: with the VSTestRunner plugin, the way to find test dll files is different.
Use the testfiles parameter directly, the Jenkins plug-in will convert the path to the real path.
It does not support the transmission of wildcard parameters.
It will call getTestFilesArguments function to obtain the full path of the file. Use the'** *tests.dll' parameter, and getTestFilesArguments function will return no files matching.
You could try to use cmdLineArgs like :
vsTest settings: "testexecute.runsettings", cmdLineArgs: "** *tests.dll"
this appears to still be an issue in 1.0.7, unable to use the plugin at all.