Need some help here. I have TestExecute installed on a remote computer, I can successfully run the test from another machine via a Task from the NetWorkSuite - that is fantastic.I need to setup the remote machine to run the tests daily, from a Scheduled Task for example. I have tried to create the Task as suggested on the Help from TestExecute (Scheduling TestExecute Runs), but I am facing two problems - (1) The project never actually runs, the Windows Task is running but nothing is happening with TestExecute(2) If the machine is locked, how can you pass parameters to the Windows Task to login before starting the Task?Thanks in advance for your time and attention.

The task runs if I set to "Run only when user is logged on," otherwise the process starts (seen from task manager) but nothing happens.???

Couple of things:1) What is the command line that you are using in your scheduled task? 2) If your test will be interacting with a UI, you cannot "lock" the workstation. You'll need to have it logged on to the desktop at the time of startup.

Thanks Robert, is there a technique I can use to unlock the station right before the test runs?

Or better yet, how am I going to run my interactive tests at midnight if I cannot logon into the machine?

Here's the article with the best techniques for this:http://smartbear.com/support/viewarticle/12567/

Scheduling TestExecute | SmartBear Community

fmendes
Contributor
13 years ago
Nevermind, found the problem - "If I run the Scheduled Task (command above) with security "Run wheather user is logged on or not" it logs on to Machine B and runs the test"

It helps to enter to correct password LOL.

Thanks for all the help!
ArtemS
SmartBear Alumni (Retired)
13 years ago
Hello,

The slave machine can be locked. Once the network suite is started on a master machine, it would perform the logging in with the specified credentials.

However, to start a scheduled project on a master machine, you should comply with any of the following conditions:

If the scheduled task has the "Run only when user is logged on" option, then the master machine should NOT be locked at the moment the task is trigged.

If the scheduled task has the "Run whether user is logged on or not" option, then the machine could be locked, but, in this case, the master TestComplete/TestExecute project should be launched with the /SilentMode command-line parameter.

Regards, Artem.
fmendes
Contributor
13 years ago
Back again. I scheduled my task for 12:00am, this morning when I checked the Task Scheduler the task is still running, logged in the Slave machine and see the TestExecute has started BUT no tests are running. Any more suggestions?

Thanks all.
ArtemS
SmartBear Alumni (Retired)
13 years ago
Hello,

Hmm, that's strange. We tried to reproduce the same scenario, and the slave projects were fulfilled successfully.

Maybe the remote computer was not configured properly (see Requirements for Remote Computers and Projects), or a user session was not opened (see Opening User Sessions on Remote Computers).

Are there any test logs on a slave machine that were created during this scheduled launch? They could clarify the problem.

Regards.

Forum Discussion

Scheduling TestExecute

Related Content

Can't trigger TestExecute through Task Scheduler

Scheduling automated TestComplete Script on TestExecute machine

testexecute from scheduler possible to activate desktop session

TestExecute 12 'dotNET' is undefined using windows task scheduler

Scheduled test runs

Recent Discussions

Onscreen Object Selector Slowness

aqObject.CheckProperty() slowness

Problem with generated data table and keyword test

WebView2 support does not work

System checks for Object for every test