[Expand]General Information/viewarticle/88628/
 [Expand]Using Help System/viewarticle/81465/
 [Expand]Getting Started Tutorial/viewarticle/82003/
 [Collapse]Using TestComplete/viewarticle/84431/
  [Expand]TestComplete User Interface, Projects and Settings/viewarticle/87798/
  [Collapse]Creating, Recording and Running Tests/viewarticle/88044/
   [Expand]Naming Objects/viewarticle/82017/
   [Expand]Creating Tests/viewarticle/83818/
   [Expand]Managing Tested Applications/viewarticle/85827/
   [Expand]Checkpoints and Stores/viewarticle/82018/
   [Collapse]Running Tests/viewarticle/83220/
     Running, Pausing and Stopping Automated Tests/viewarticle/82829/
     Stopping Tests on Timeout/viewarticle/83706/
     Scheduling Automated Tests/viewarticle/84167/
     Creating Batch Test Runs/viewarticle/85275/
    [Collapse]Running Tests via Remote Desktop/viewarticle/81143/
      Running Tests via Remote Desktop - Overview/viewarticle/83996/
      Running Tests in Minimized Remote Desktop Windows/viewarticle/85926/
      Disconnecting From Remote Desktop Session While Running Automated Tests/viewarticle/86476/
      Smart Resizing of Remote Desktop Windows/viewarticle/83007/
     Running Tests on Locked Computers/viewarticle/83881/
     Shutting Down and Restarting Computer After Test Run/viewarticle/81002/
     Rebooting Computer During Automated Tests/viewarticle/80655/
     Using TestComplete Indicator/viewarticle/81103/
    [Expand]Running Tests - Tips/viewarticle/87930/
     Running Tests - Specifics/viewarticle/88875/
   [Expand]Handling Playback Errors/viewarticle/84986/
   [Expand]Keyword Testing/viewarticle/80985/
   [Expand]Test Visualizer/viewarticle/80575/
   [Expand]Exploring Applications/viewarticle/80624/
   [Expand]Debugging Tests/viewarticle/83018/
  [Expand]Test Results/viewarticle/80579/
  [Expand]Enhancing Tests/viewarticle/83506/
  [Expand]Teamwork and Integration Into QA Process/viewarticle/84972/
  [Expand]Extending TestComplete/viewarticle/81408/
  [Expand]Automating TestComplete/viewarticle/88022/
  [Expand]Best Practices/viewarticle/87218/
 [Expand]Testing Types/viewarticle/85355/
 [Expand]Applications Testing/viewarticle/83383/
 [Expand]Working With Application Objects and Controls/viewarticle/81481/
 [Expand]Samples and Tutorials/viewarticle/81997/
 [Expand]Other Tools That Help You Test Better/viewarticle/82893/
 [Expand]TestComplete Licensing Guide/viewarticle/88365/
Updated: 10/12/2016 Applies To: TestComplete 12 Rating: No votes Click to rate: PoorNot badAverageGoodExcellent
Running Tests via Remote Desktop

Running Tests via Remote Desktop - Overview

Information in this topic applies to desktop and web applications.

The Remote Desktop is a built-in Windows feature that lets you access a Windows session running at one computer from another computer. In order to use the Remote Desktop, the workstation on which TestComplete or TestExecute will be running must have special server-side software. This software may be included in the operating system (like it is included in Windows XP), or it can be a third-party software like VNC, DameWare or NetOp.

The Remote Desktop feature lets you perform a variety of tasks. For example, you can use the Remote Desktop if you need to:

  • Observe the tested application’s behavior on remote computers.

  • Run tests on remote computers.

  • Run tests on computers that are locked due to security purposes (see Running Tests on Locked Computers).

  • View and analyze results on test runs on one or several remote computers, and save them to a local computer.

  • And so on.

To run tests on Remote Desktop, follow these steps:

  1. If needed, lock the computer where TestComplete (TestExecute) is installed.

  2. Log on to the TestComplete (TestExecute) workstation via the Remote Desktop Connection from another computer.

  3. Start running tests with TestComplete (TestExecute).

TestComplete (TestExecute) will run tests in the Remote Desktop session, the same way as if they were running from the remote computer itself.

Some important notes:

  • When running GUI tests via Remote Desktop, do not do the following:

    • Do not lock the computer.
      See the tips below.

    • Do not disconnect from the Remote Desktop Connection session.
      See the workaround below.

    • Do not minimize the Remote Desktop window.
      See the workaround below.

    When you do any of these, the operating system switches the Remote Desktop session to the GUI-less mode and does not draw the GUI. In this case, TestComplete fails to interact with the GUI and the test fails.

    We would like to note that these restrictions apply only to tests that involve interaction with the GUI. As for other tests, they can be run if the Remote Desktop window is minimized or if you disconnect from the Remote Desktop.

    Tips and workarounds:

    • To prevent the computer from locking automatically during the test run, do the following:

      • Disable the screen saver.

      • Disable power saving options that may turn off the computer or its display, such as Put the computer to sleep.

      • Disable the Windows logon screen.

    • If you need to disconnect from the Remote Desktop session, you can retarget the session to the remote computer’s console before starting your tests. For detailed information, see Disconnecting From Remote Desktop While Running Automated Tests.

    • If you need to minimize the Remote Desktop window, you need to change the Registry settings on your local machine. See Running Tests in Minimized Remote Desktop Windows.

  • If you need to resize the Remote Desktop window, you can do this by setting certain values for the connection properties. For more information on how to do this, see Smart Resizing of Remote Desktop Windows.

  • When running tests on a remote computer that participates in distributed testing, TestComplete creates a Remote Desktop session and automatically sets the master computer's screen resolution on the remote computer. This is done to avoid possible problems with test running.

  • You open several user sessions to the same server computer. The number of TestComplete instances that can work concurrently in sessions depends on your license.

    If you have a Node-Locked license, then only one TestComplete instance can run on the server computer at a time. That is, you can use TestComplete in one user session only.

    If you have a Floating User license, then the number of TestComplete instances that can run concurrently is determined by the license key. That is, the number of user sessions, in which you can use TestComplete, cannot exceed the limit set by the license.

    If you want to use TestComplete in several user sessions connected to the same server, we recommend that you install and use a TestComplete Floating User license for the desired number of instances on the server. Alternatively, to run tests in user sessions, you can install and use TestExecute.

See also
Running Tests via Remote Desktop | Running Tests in Minimized Remote Desktop Windows | Smart Resizing of Remote Desktop Windows | Disconnecting From Remote Desktop While Running Automated Tests | Running Tests | Running Tests on Locked Computers

© 2016 SmartBear Software. All rights reserved.
Email Send feedback on this document