Can't trigger TestExecute through Task Scheduler

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

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?

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.

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\

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?

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. 

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?

Oops! That should be /Run and /End.

Entering schtasks /?, displays the various commands

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?