Forum Discussion

fmendes's avatar
fmendes
Contributor
14 years ago

Scheduling TestExecute

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.
  • fmendes's avatar
    fmendes
    Contributor
    14 years ago
    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.



    ???
  • tristaanogre's avatar
    tristaanogre
    Esteemed Contributor
    14 years ago
    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.
  • fmendes's avatar
    fmendes
    Contributor
    14 years ago
    Thanks Robert,

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

  • fmendes's avatar
    fmendes
    Contributor
    14 years ago
    Or better yet, how am I going to run my interactive tests at midnight if I cannot logon into the machine? 
  • fmendes's avatar
    fmendes
    Contributor
    14 years ago
    Robert, thanks again. I have read the article, I apologize but I still fail to see how this can be automatted to run at midnight for example. As far as I can understand I would still need to logon to a machine to run the tests locally or remotely. Please advise.
  • Oleg's avatar
    Oleg
    Occasional Contributor
    14 years ago

    Hey Luis,


    if I understand your problem correctly - you need to keep you machine 'unlocked' for the moment, when tests should be executed with TestExecute. You can do it - you can just 'close' your Remote Desktop session in the way, when machine is not locked.


    Oleg.



  • fmendes's avatar
    fmendes
    Contributor
    14 years ago
    Here is the scenario I want to accomplish:



    Machine A - development machine with TestComplete and the Master NetworkSuite project

    Machine B - test machine with TestExecute and Slave NetworkSuite project



    I leave the office at 5:00pm, both machines are locked. I would like to know how can I tell Machine B run the tests at 12:00am





    Right now I can tell Machine B to run the tests by just starting the task on the Master from Machine A. The task will logon to Machine B, run the tests and upload the results back to Machine A. This works great!



    But, when I am not in the office at midnight, how can I tell Machine B run the tests?
  • Oleg's avatar
    Oleg
    Occasional Contributor
    14 years ago

    Sorry, maybe it's a bit late here but I still can't understand the root of the problem. I thought that you were having problems with locked machines when you log off from Remote Desktop session - because I've faced them and I spent some time trying to find appropriate solutions.


    But in your case - machine A (master) and machine B(slave) are locked starting from 5 p.m. If machine A has scheduled task for midnight - what can prevent it from starting the tests on machine B? It's not the problem that machine B will be locked locked - because TestComlete/TestExecute can successfully login if you specify appropriate credentials in the settings of you Network task. It's also not the problem, that machine A will be locked  - there is not UI needed for A to run tests on B and gather results.


    So, everything that you need to do - organize the right communication between A and B. Just invoke Slave task run from in the script, that is executed on Master and that's it.


  • fmendes's avatar
    fmendes
    Contributor
    13 years ago
    Thanks Oleg, still no luck.



    If I setup a schedule to run from Machine A (master) and the security is set to "Run only when user is logged on" is works fine, same as if I setup the task directly on Machine B (slave). However, as I mentioned, I need to run this task at a time I am not in the office therefore I need to select "Run wheather user is logged on or not" - but setting up the task with this security it doesn't work.



    The task on Machine A (Master)



    C:\Program Files (x86)\Automated QA\TestComplete 8\Bin\TestComplete.exe" "C:\Workspace\SCC\TestComplete8 Projects\MySuite.pjs" /r /p:Master /t:"Script|TaskLauncher|StartTasks" /run /exit



     - If I run the task directly it logs on to Machine B and runs the test.

     - If I run the script directly it logs on to Machine B and runs the test.

     - If I run the Scheduled Task (command above) with security "Run only when user is logged on" it logs on to Machine B and runs the test.

     - 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.