Details
-
Type:
Bug
-
Status: Open (View Workflow)
-
Priority:
Blocker
-
Resolution: Unresolved
-
Component/s: vstestrunner-plugin
-
Labels:
-
Environment:Jenkins 2.73.2
VSTestRunner plugin 1.0.5
-
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.
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"