Articles

[Collapse]TestComplete/viewarticle/63445/
 [Expand]General Information/viewarticle/63445/
 [Expand]Using Help System/viewarticle/55799/
 [Expand]Getting Started Tutorial/viewarticle/56246/
 [Expand]Using TestComplete/viewarticle/57875/
 [Collapse]Testing Types/viewarticle/62721/
  [Expand]Functional Testing/viewarticle/64013/
  [Expand]Unit Testing/viewarticle/57277/
  [Expand]Data-Driven Testing/viewarticle/56219/
  [Expand]Regression Testing/viewarticle/57279/
  [Collapse]Distributed Testing/viewarticle/55046/
   [Expand]Distributed Testing - Basic Concepts/viewarticle/62720/
    Distributed Testing - Requirements/viewarticle/56621/
   [Expand]Creating and Running Distributed Tests/viewarticle/62717/
    Monitoring Network Suites/viewarticle/57741/
    Network Suite Log/viewarticle/56373/
   [Expand]Synchronizing Projects in Network Suites/viewarticle/57742/
   [Expand]Managing Network Suites/viewarticle/56559/
   [Expand]Network Suite Variables/viewarticle/56547/
    About TestComplete Service/viewarticle/55560/
  [Expand]Parallel Testing/viewarticle/62722/
  [Expand]Coverage Testing/viewarticle/55234/
   Load Testing/viewarticle/62753/
 [Expand]Applications Testing/viewarticle/62606/
 [Expand]Working With Application Objects and Controls/viewarticle/55815/
 [Expand]Samples and Tutorials/viewarticle/56239/
 [Expand]References/viewarticle/57878/
 [Expand]Other Tools That Help You Test Better/viewarticle/63442/
 [Expand]TestComplete 10 Licensing Guide/viewarticle/63451/
Updated: 9/23/2014 Applies To: TestComplete 10 Rating: Not badNot badNot badNot badNot bad 2 vote(s) Click to rate: PoorNot badAverageGoodExcellent
Distributed Testing

Distributed Testing - Requirements

Information in this topic applies to desktop and web applications.

Common Requirements

Each computer (whether master or remote) used in distributed testing must be configured as follows:

  • TestComplete 10 or TestExecute 10 must be installed on the computer.

    Use the same version of TestComplete and TestExecute on all computers.
  • TestComplete 10 Service must be running on the computer (by default, the service is launched automatically at Windows startup).

  • If a firewall or antivirus is installed on the computer:

    • Add TestComplete 10, TestExecute 10 and TestComplete 10 Service to the list of trusted applications. To learn how to allow TestComplete through the built-in Windows Firewall, see TestComplete and Windows Firewall.

    • Allow traffic through the TCP ports used by TestComplete and TestComplete Service. By default, these ports are 6020-6022. You can change the ports in the Network Suite Options.

  • The TCP ports for remote connections in the Network Suite Options must be the same on all computers.

  • On Windows XP and Windows Server 2003, install the Remote Desktop Connection 6.0 client from here:

    http://support.microsoft.com/kb/925876

Configuring Remote Computers

1. Enable Remote Desktop Connection

To run distributed tests on remote computers, you need to enable remote desktop connections to them. You also need to add the user accounts for remote login to the Remote Desktop Users group on the remote computers. To do this:

  • Open the Control Panel | System applet.

  • On Windows 8 and Windows Server 2012:

    • In the left part of the System window, click Remote settings.

    • In the dialog that opens, select Allow remote connections to this computer.

    • Clear the Allow connections only for computers running Remote Desktop with Network Level Authentication (recommended) check box.

      Remote desktop settings for Windows 8

    On Windows Vista, Windows 7 and Windows Server 2008:

    • On the left of the System window, click Remote settings.

    • In the dialog that opens, select the Allow connections from computers running any version of Remote Desktop (less secure) check box (or similar).

      Remote desktop settings for Windows 7

    On Windows XP and Windows Server 2003:

    • In the System Properties dialog, switch to the Remote page.

    • Select the Allow users to connect remotely to this computer check box (or similar).

  • Click Select Users. The Remote Desktop Users dialog opens.

  • Specify the user accounts allowed to access the computer, and click OK.

    Note: You will use these accounts in your master test project to log in to the remote computers.
    Note: These user accounts must have non-empty passwords.
  • Click OK to close the System properties and save the changes.

2. Configure the Privilege Level for TestComplete (TestExecute)

On remote computers with Windows 8, Windows 7, Windows Vista, Windows Server 2012 or Windows Server 2008, choose whether to run TestComplete (TestExecute) with administrator privileges:

  • If TestComplete (TestExecute) does not need administrator privileges to run the slave project, configure TestComplete (TestExecute) to run without them. To do this:

    • On the remote computer, open Windows Explorer or any other file manager and find the executable file of TestComplete (TestExecute). The file name is <TestComplete 10>\Bin\TestComplete.exe for TestComplete and <TestExecute 10>\Bin\TestExecute.exe for TestExecute.

    • Right-click the TestComplete (TestExecute) file and select Properties from the context menu.

    • In the file properties dialog, switch to the Compatibility tabbed page.

    • Uncheck the Run this program as an administrator option.

    • Click OK.

  • If TestComplete (TestExecute) needs administrator privileges to run the slave project, disable User Account Control (UAC) on the remote computer. To learn how to disable UAC, see Testing Applications With TestComplete Under Windows Vista and Later Operating Systems.

    Disabling UAC reduces Windows security.

3. Configure Windows Server Computers

If a remote computer is running a server edition of Windows, you need to enable the Restrict each user to one session option in the Terminal Services Configuration:

  • On the remote computer, click Start | Administrative Tools | Terminal Services Configuration. This will open the Terminal Services Configuration window.

  • In the left pane of the Terminal Services Configuration window, click the Server Settings node. The right pane of the window lists the server settings you can modify.

  • Double-click Restrict each user to one session in the settings list.

  • In the dialog, enable the Restrict each user to one session option and click OK.

Also, if a remote computer is running in the Remote Administration Server mode and there are user sessions opened on it, you need to close unnecessary sessions. To do this:

  • Log on to the remote computer locally.

  • Click Start | Administrative Tools | Terminal Services Manager. This will open the Terminal Services Manager window.

  • Select the server in the left pane of the Terminal Services Manager window. In the right pane of the window, switch to the Users tabbed page.

  • If there are several remote sessions, select one of the users with the Remote Desktop Protocol session, right-click it and select Log Off in the context menu.

4. Disable Group Policies

You need to disable the following group policies on the remote computers:

  • Always prompt client for password upon connection

  • Prompt for credentials on the client computer (on Windows Vista and later)

Note: If the remote computer belongs to a domain, these group policies must also be disabled on the domain controller. Ask your system administrator to do this.

To disable these policies:

  • Click Start, select Run, type gpedit.msc and press Enter. This will open the Group Policy Editor.

  • In the tree on the left, select the following category:

    On Windows 8, Windows 7 and Windows Server 2012:

    Local Computer Policy | Computer Configuration | Administrative Templates | All Settings

    On Windows Vista and Windows Server 2008:

    Local Computer Policy | Computer Configuration | Administrative Templates | Windows Components | Terminal Services | Terminal Server | Security

    On Windows XP and Windows Server 2003:

    Local Computer Policy | Computer Configuration | Administrative Templates | Windows Components | Terminal Services | Encryption and Security

  • In the list on the right, double-click the Always prompt client for password upon connection item.

  • Select Disabled and click OK.

If the remote computer runs Windows 8, Windows 7, Windows Vista, Windows Server 2012 or Windows Server 2008, also do the following:

  • In the tree on the left, select Local Computer Policy | Computer Configuration | Administrative Templates | All Settings.

  • In the list on the right, double-click the Prompt for credentials on the client computer item.

  • Select Disabled and click OK.

Test Project Requirements

  • For each computer in the master project’s Hosts collection, you must specify the user account (domain, user name and password) to log in to that computer.

    Alternatively, you can specify a common user account for multiple hosts in the network suite properties of the master project.

    Note: User accounts must have non-blank passwords.
  • The master project’s NetworkSuite project item must have the Jobs collection with a list of jobs to run. Each job must have at least one task.

  • For each task in the master project, you must specify a host on which the task will be run (the Host property) and the test that will be run (the Project file name and the Test properties).

  • Remote computers must have access to the projects they will run. That can be done in the following ways:

    • The projects can be placed in the specified folders on the remote computers where they will be run.

      If the tests belong to your master project or to other projects residing on the master computer, you can configure the master project to copy them to the appropriate remote computers automatically or you can copy them manually. See Copying Slave Projects to Remote Computers.

      Note: If you use the Network Suite wizard to create distributed tests, your master project is configured to copy the corresponding tests from the master project to the remote computers automatically.
    • The projects can be located in a shared network folder. In this case, the user accounts used to log in to the remote computers must have read and write permissions for this shared folder.

      Note: We do not recommend that you share the same project or project suite among several computers, as the computers may fail to open the shared project or project suite simultaneously.

Required Plug-Ins

The distributed testing functionality is implemented by the following plug-ins. They are installed and enabled automatically during TestComplete installation.

Plug-In Name Description
Network Suite Provides the NetworkSuite project item (which must be added to projects manually) and the NetworkSuite scripting object, which is available if the project has the NetworkSuite item.
Host List Editor Provides the Hosts editor that lets you configure the list of hosts (i.e. computers that can take part in distributed testing controlled from the given project), and set up properties of individual hosts.
Job List Editor Provides the Jobs editor that lets you configure the list of jobs (collections of tasks) that belong to the network suite of the given project, and set up properties of individual jobs.
Task List Editor Provides the Tasks editor that lets you configure the list of tasks that belong to the given job in the network suite, and set up properties of individual tasks.
Run State Provides the Run State page for the NetworkSuite project item editor, which lets you monitor the network suite, job or task run.

Note that the Network Suite plug-in must be enabled in TestComplete (TestExecute) on both master and remote computers.

If you experience issues when working with network suites, you can check whether the plug-ins are enabled in the File | Install Extensions dialog.

See also
Distributed Testing | About Master and Slave Projects | Copying Slave Projects to Remote Computers | Opening User Sessions on Remote Computers | Creating and Running Distributed Tests | Running the Network Suite, Jobs and Tasks


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