Batch file command do not delete TestExecute process running last time
We are using batch file to run our TestComplete Tests on TestExecute machine . Attached below here is the batch file. We have already included the command to check whether testExecute process is running . if it isrunning then it should kill before starting new tests.
It is not working any more .
I have manually opened the TestExecute . Then I ran the batch file . But it do not kill the TestExecute process and no tests get started.
Any idea what is missing here.
Solved! Go to Solution.
I use these lines for myself:
REM Check if an instance is on memory, if not go directly to run, if yes kill this instance
tasklist | find "TestExecute.exe" /C /i > nul
if ERRORLEVEL 0 goto Start1
taskkill /f /im TestExecute.exe
Un sourire et ça repart
Look like TesExecute.exe process name get change to TESTEX~1.exe
Dicussed the issue with support team , they have asked me to repair the TestExecute but it did not work . After that they have no idea what causes this name change ?
Finally I tried to uninstall and install the fresh TestExecute and then the correct name appears . Not sure how the name chanes,
Now I am concerned if the name change may occur in the future as support team do not know what causes this issue ?
> Look like TesExecute.exe process name get change to TESTEX~1.exe
As a wild guess: the name change looks like the old DOS name. Would you mind to talk to your IT department and wonder if they ever heard about something like that been caused by some OS system setting/update/etc. ?
/Alex [Community Hero]
[Community Heroes] are not employed by SmartBear Software but
are just volunteers who have some experience with the tools by SmartBear Software
and a desire to help others. Posts made by [Community Heroes]
may differ from the official policies of SmartBear Software and should be treated
as the own private opinion of their authors and under no circumstances as an
official answer from SmartBear Software.
The [Community Hero] signature is used with permission by SmartBear Software.
As far as I can see, the issue was solved by reinstalling TestExecute - I checked the support case. Let me mark this workaround as a solution here.
Community and Education Specialist