Forum Discussion
my Azure pipelines are running successfully now. i'm am no longer getting the "Cannot start process because a file name has not been provided." error message. the only change I made was to ensure TestExecute is active before the pipeline kicks off. Before, TextExecute was not actively running on the VM (which is the way I've had it set up for almost a year) and the pipeline would start TE, run the test scripts and then exit TE when the pipeline completed. something has changed in the latest release(s) that seems to have altered that feature. Can anyone else confirm this as a solution?
Sadly this solution would not work for me since i need to pass some variables to TestExecute using /Pvar.
This only seems to work when testexecute is not already running.
- dhundley2 years agoRegular Contributor
i understand. still curious if anyone else (who doesn't have that need) could confirm that something has been changed in recent releases (i installed 15.52 and experienced the same behavior) that is preventing an Azure pipeline from starting and ending testexecute using the classic editor? are there new fields that have to be set or something? or is this a bug that will be fixed in the next release so i can go back to how mine was before?
- dfajardo2 years agoNew Contributor
Its my belief that Microsoft changed the VSTest task from 2.220.0 to 2.224.0 and something is different that is messing with TC test.
Related Content
- 12 years ago
- 14 years ago
- 8 years ago
Recent Discussions
- 3 days ago