I am trying to trigger TestExecute by using a .bat file through Task Scheduler. When I try trigger .bat file manually TestExecute triggered successfully. But if I try to trigger by using Task Scheduler the status is changed from Ready to Running, but we can't see anything in the background. Please check below screenshot. Below code is the .bat file, Please verify it. Echo offcd "C:\Program Files (x86)\SmartBear\TestExecute 15\Bin"start "" /wait "C:\Program Files (x86)\SmartBear\TestExecute 15\Bin\TestExecute.exe" "C:\Users\ravikaanth.ns\Documents\MB_Automation\TestProject2\MBAutomation1.pjs" /run /project:"MBAutomation1" /unit:"CampaignReadProd" /routine:"readCampaign"

I've just ran the same, these are the results. Also, TC has generated log files too.My batch file has only this command, start "TestExecute" /wait "C:\Program Files (x86)\SmartBear\TestExecute 15\x64\Bin\TestExecute.exe" "C:\Sandbox\TestComplete\Project Flow\Project Flow.pjs" /run /exit /DoNotShowLog /project:"TestProject2" /ExportLog:"C:\Sandbox\Log\TestProject2\index.html" And task schedular How are you running your Task? Is this on your local machine?

Can't trigger TestExecute through Task Scheduler

rraghvani
Champion Level 3
2 years ago
I've just ran the same, these are the results. Also, TC has generated log files too.
My batch file has only this command,

start "TestExecute" /wait "C:\Program Files (x86)\SmartBear\TestExecute 15\x64\Bin\TestExecute.exe" "C:\Sandbox\TestComplete\Project Flow\Project Flow.pjs" /run /exit /DoNotShowLog /project:"TestProject2" /ExportLog:"C:\Sandbox\Log\TestProject2\index.html"

And task schedular

How are you running your Task? Is this on your local machine?
AlexKaras
Champion Level 3
2 years ago
Hi,

It is my guess that you are trying to execute tests against the GUI-based application.

If my guess is correct, than not locked active user session must exist for the user that is used to run the test.

In order to get this you must:

-- Always keep this user logged-on and desktop for this user must never be locked;

-- Task in the Task Scheduler must be configured to be executed on behalf of this user and be allowed to interact with the desktop.

https://support.smartbear.com/testcomplete/docs/testing-with/running/scheduling.html

rraghvani

Champion Level 3

2 years ago

Can you try with just this command line.

start "TestExecute" /wait "C:\Program Files (x86)\SmartBear\TestExecute 15\x64\Bin\TestExecute.exe "C:\Users\ravikaanth.ns\Documents\MB_Automation\TestProject2\MBAutomation1.pjs" /run /exit /DoNotShowLog /project:"MBAutomation1"

Run your batch file manually, just to test that it works.

What command and parameters are you using to call you batch file in Task Scheduler?

Ravikaanth
Contributor
2 years ago
rraghvani Thanks for your guidance, Your code works when I try to run it manually. But in Task Scheduler it is showing only Task triggered message but we can't see anything in the background. Please check below image I am using the .bat file location for Program/Script and we are not passing any arguments or parameters.
rraghvani
Champion Level 3
2 years ago
If you Program/script location is,
C:\Users\ravikaanth.ns\Desktop\TestExecuteRun.bat
Then can you put the following path in Start in (optional),
C:\Users\ravikaanth.ns\Desktop\
- Ravikaanth
  Contributor
  2 years ago
  I tried your suggestion but still it looks same. Status changed to running but nothing is triggering.
  - dhundley
    Regular Contributor
    2 years ago
    i have a testcomplete project/testitem that i would like to be able to schedule using the Task Scheduler and I have been trying everything I can think of and have been able to research on the internet and simply cannot get it to work. First, it should be said that i can bring up a command prompt window on the VM where I want this to run and i can manually run testexecute with a command line argument list that runs it perfectly. if i simply try to stick that into the task scheduler i get a message indicating that the "requested operation requires elevation". so i have placed the call to testexecute with the argument list into a powershell script called runTcAsAdmin.ps1 and I can manually run that successfully. i created a bat file called runTcAsAdmin.bat into which I placed the following code
    
    Echo OFF
    PowerShell.exe -NoProfile -Command "& {Start-Process PowerShell.exe -ArgumentList '-NoProfile -ExecutionPolicy Bypass -File ""%~dpn0.ps1""' -Verb RunAs}"
    
    and directed by Task Scheduler job to run the bat file. After i run it the Last Run Result message indicates "the operation completed sucessfully" but it didn't do anything that was in the script (like it does when i run the script manually using the command prompt or the powershell script).
    
    my ps1 file looks essentially like this:
    
    Start-Process -FilePath "C:\Program Files (x86)\SmartBear\TestExecute 15\x64\Bin\TestExecute.exe" -ArgumentList "/exit /run <fully qualified path>\<project suite name>.pjs /p:<project name> /t:ProjectTestItem1"
    
    what step or parameter am i missing? does it matter the order of the command line parameters for testexecute?
dhundley
Regular Contributor
2 years ago
i am trying to do this for the first time. normally i don't try to schedule a testcomplete automation script to run on a VM using the task scheduler but i would like to figure out how its done. i have been at this all day trying one thing and then another but nothing works. it should be noted however that the project/testitem does run successfully if i manually kick it off so there's nothing wrong with the script, per se. this is essentially it

"C:\Program Files (x86)\SmartBear\TestExecute 15\x64\Bin\TestExecute.exe" -ArgumentList "/exit /run <full qualified path>\<project suite>.pjs /p:<project name> /t:ProjectTestItem1"

First, i attempted the simple approach and just configured the Edit Actions of the scheduled task to start the testexecute application and put the command line arguments in the Add arguments box. that resulted in a Run Result message of "the request operation requires elevation"

Next, i created a powershell file called runTcAsAdmin.ps1 containing a single line with a "Start-Process -FilePath" appended to the front of the call to TestExecute followed by its list of command line arguments. I put powershell.exe in the program/script box of the task scheduler and put the following powershell arguments in the Add arguments box

-Command Start-Process PowerShell -ArgumentList '-File <fully qualified path name>\runTcAsAdmin.ps1' -Verb RunAs

That one finished with "The operation completed successfully" in the Run Result message but it didn't do anything that the automation script was designed to do.

Finally, i tried creating a bat file called runTcAsAdmin.bat with the following contents and in the same location as the runTcAsAdmin.ps1 file and i changed the Task Scheduler Action so that it points to this bat file

Echo OFF
PowerShell.exe -NoProfile -Command "& {Start-Process PowerShell.exe -ArgumentList '-NoProfile -ExecutionPolicy Bypass -File ""%~dpn0.ps1""' -Verb RunAs}"

but that had the same result as the previous attempt. Does anyone have something working for this? what step or parameter am i missing?
dhundley
Regular Contributor
2 years ago
sorry about the double post. after i finished the first time i looked for it and didn't see it listed in the thread so i typed it in again. then both of them showed up.
- rraghvani
  Champion Level 3
  2 years ago
  In your batch file, have the following command (adjust according to your project)
  
  "C:\Program Files (x86)\SmartBear\TestExecute 15\x64\Bin\TestExecute.exe" "C:\Temp\MyProject\MyProject.pjs" /run /exit /DoNotShowLog /project:"MyProject" /ExportLog:"C:\Temp\MyProject\index.html"
  
  Run the batch file from the command prompt, to ensure that it works.
  
  Once you have confirmed that the above is working. Create a Task Schedule, see my previous responses and screenshots. You also need to set the following options,
  
  Run the task from Computer Management, to ensure that it works.
  
  While you are still logged into the VM, on your local machine, launch Computer Management. Right click on Computer Management (Local) and select Connect to another computer. Enter the details of your VM. From here, run the task and you should then see the automation running on your VM.
  
  See Using TestComplete With Administrator Privileges
  
  To check that you have Elevated Permissions, right click e.g. either Edge or Chrome icon, then right click either Edge or Chrome from the menu item, and you should see the option to Run as administrator
  
  If you don't see this, then you don't have Elevated Permissions. You will need to your IT team to get the appropriate permissions.
  - dhundley
    Regular Contributor
    2 years ago
    
    rraghvani
    
    i created the bat file as you instructed and i was able to successfully run it using a command prompt window. i set up my scheduled task also as you instructed, however, when i connected to the remote computer (using computer management) and accessed the task scheduler, the list of tasks was empty so i couldn't run it from there. i am able to run as admin any application (chrome, edge, command prompt, etc) on the VM but when i run the scheduled task on the VM it goes into a 'running" state but nothing in the script ever happens (the very first thing which would be starting testexecute) and i eventually have to manually End the run. i even tried to add the "start 'mytitle' \wait" at the beginning of the command line in the bat file (as you had instructed in the posts from several months ago) but that resulted in the same thing. nothing happens other that it says it's running and i have to manually End the scheduled task.
    
    the only way i've ever been able to get something to run on my VM that requires elevated permissions is by having the scheduled task point to the bat file and the bat file points to a powershell script that contains the actual steps to execute and the bat file call to the ps1 file utilizes the -Verb RunAs argument to elevate the permissions. I just can't don't think I'm setting up my powershell script for running test execute with command line arguments correctly. have you (or anyone else reading this) ever set up a scheduled task on a VM using this method? I'm certainly open to trying anything else you might suggest but, so far, i still haven't been able to get it to work.
    
    thanks!
rraghvani
Champion Level 3
2 years ago
What about configuring your task 'Agent1' like so,

and then use the command prompt to start the agent,

schtasks.exe /Start /TN Agent1

or stop the agent

schtasks.exe /End /TN Agent1

Would that work?
- dhundley
  Regular Contributor
  2 years ago
rraghvani
Champion Level 3
2 years ago
Oops! That should be /Run and /End.

Entering schtasks /?, displays the various commands
- dhundley
  Regular Contributor
  2 years ago
  it still puts the agent.listener under the background processes
  
  the ONLY method i have found so far that will run the agent as an App is from TestExcecute as a TestedApp. if i could just get the testexecute command line to run via a scheduled task, bat file or powershell script i'd be in business but can't get that to work either.
rraghvani
Champion Level 3
2 years ago
What I don't really understand, is why do you need to run the Agent as an app. Are you interacting with the following output shown by the Agent in anyway?
- dhundley
  Regular Contributor
  2 years ago
  i know i pasted the screenshot that explains this reasoning, but, as you have pointed out, this new forum setup appears to be omitting certain posts because i've scrolled up and down and don't see it now. I'll try to explain again and the link to the explanation is:
  
  https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/agents?view=azure-devops&tabs=yaml%2Cbrowser#interactive-or-service
  
  This Agent.Listener application is for our Azure Devops system. We have Azure pipelines that have been created by TestComplete for browser based applications that are directed to run on the VM where this agent is running. so, we are "running UI tests" therefore the agent listener has to be running "As an interactive process with auto-logon enabled". if the listener is not in the Apps section (but instead in the Background process) then it is not interactive and the pipelines will not run. i realize that what i'm trying to do with this one script is not a UI but everything else we run on this VM is a UI test so that is how the agent listener has to run.
  
  You've tried your best. i really appreciate the amount of effort you have put into this but I'm getting to the point where I'm ready to give up. there just doesn't seem to be an answer for this. It's like a Catch-22. Thanks again!