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?
- dhundley2 years agoRegular Contributor
just to add one thought to this, at our company i can probably get away with leaving TestExecute active 24x7 because we have a sufficient number of licenses for me to do that but for anyone who has multiple developers sharing licenses it's beneficial to not leave it active all the time. that's tying up a license when it's not really being used.
- SlickRick2 years agoContributor
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.
- dhundley2 years agoRegular Contributor
i just returned from vacation to discover that none of my automated testcomplete pipelines will run EVEN WHEN testexecute is actively running on the VM (see my post from 7/28). now, with TE running, i'm seeing this error
Unable to connect to TestExecute: it is running with different rights, or its state is incorrect. Please close it and try again.
i have tried closing and restarting testexecute both normally and running as admin but nothing works.
when is that new release available? if not today, then which previous version does work?
Given the recent fiasco with the Chrome and Edge browsers and now this, i'm beginning to regret the recommendation i made to the management at my company to abandon Ranorex in favor of TestComplete. What is it with SmartBear lately that is causing all these show stopping issues to occur?
Related Content
- 12 months ago
- 3 years ago
Recent Discussions
- 4 days ago
- 4 days ago