Forum Discussion

sandysang's avatar
sandysang
Contributor
2 years ago

Confirm Remote Desktop when we run testcomplete

Hi , 

when we run test complete by remote computer and use task schedule to trigger ,we find that :

 

 

Scheduler OptionRDP ConnectionStatus
Run only log onactiveSucceed
Run only log ondisconnectfailed
Run whether log on or notactivefailed
Run whether log on or notdisconnectfailed

 

so , we want to confirm that if we use task schedule we can not choose use Run whether log on or not ? from the guide document we can see this "Enable the Run only when user is logged on option for scheduled tests. These tests cannot be run with the Run whether user is logged on or not option selected, because in this case, they run in a non-interactive session and cannot interact with the GUI." but we still want to confirm it .

And we need to use one computer to connect to remote computer when we choose the method about "running test via remote desktop", if we have set the task schedule but do not use one computer to connect to the remote computer , test still failed .

 

Test Run

2 Replies

Sort By
  • rraghvani's avatar
    rraghvani
    Icon for Champion Level 3 rankChampion Level 3
    2 years ago

    For TestComplete to interact with a GUI application, an active session is required - meaning there must be a user logged onto the machine, and the machine not locked.

     

    You can use tscon utility to disconnect your session, and the active session will still remain - meaning the user is still logged on, and the machine is not locked. TestComplete can still interact with the GUI application.

     

    If there's no active session or the machine is locked, then there's no GUI. Therefore, TestComplete will fail to interact with the GUI application.

     

    This is how Windows remote desktop works.

  • Freyamarsden's avatar
    Freyamarsden
    Occasional Visitor
    2 years ago

    Hii,

     

    You are right. When using Task Scheduler to trigger TestComplete tests on a remote computer, the "Run whether user is logged on or not" option might lead to issues due to non-interactive sessions that can't interact with the GUI. The "Run only when user is logged on" option is more suitable for scheduled tests.