Requirements

Enable Remote Desktop Connections

Configure Group Policies

Disable Secure Sign-In

Disable Additional Screens

Run Jenkins in Interactive Mode

Provide Elevated Permissions for TestComplete

Prepare Jenkins Nodes to Run Tests in CrossBrowserTesting Environments

By default, your computer will prohibit remote connections. To connect to a slave machine using Jenkins under the specified user session:

1. On your slave machine, set the System properties > Remote > Remote Desktop option to:

   • In Windows 10 and Windows 8 – Allow remote connections to this computer.

   • In Windows 7 – Allow connections from computers running any version of Remote Desktop (less secure).

2. Add a user account under which you will run tests on a slave machine to the Remote Desktop Users group.

3. Make sure that the user account has a non-empty password.

Otherwise, Jenkins will not be able to connect to the remote machine and run TestComplete tests on it.

To be able to connect to a slave computer and open a user session on it, configure the following group policies on the slave computer:

1. On your slave computer, open the Group Policy editor (type gpedit.msc in the Search dialog and press Enter).

2. Disable the following policies:

   • Require user authentication for remote connection by using Network Level Authentication

   • Always prompt client for password upon connection

   • Prompt for credentials on the client computer

   To disable these policies

   To disable these policiesTo disable these policies

   1. In the tree on the left of the Group Policy editor, select the following category:

      On Windows 10, 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 > Remote Desktop Services > Remote Desktop Session Host > Security

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

      Click Disabled and then click OK.

   3. Repeat step 2 for the Prompt for credentials on the client computer and Require user authentication for remote connection by using Network Level Authentication items.

   If the computer belongs to a domain, you may need to ask your system administrator to disable these policies on the domain controller as well.

3. If the slave computer is running under Windows 10, enable the Require use of specific security layer for remote (RDP) connections group policy and set the security layer to Negotiate.

   To configure the group policy

   To configure the group policyTo configure the group policy

   1. In the tree on the left of the Group Policy editor, select Local Computer Policy > Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security.

   2. In the Setting list on the right, double-click the Require use of specific security layer for remote (RDP) connections item.

   3. In the subsequent dialog, click Enabled.

   4. In the Security Layer drop-down list of the dialog, select Negotiate.

   5. Click OK to close the dialog and save the changes.

4. If the slave computer is running under a non-server edition of Windows and it has other users logged in, log off those users.

5. If the computer is running under a server edition of Windows, enable the following policy:

   • Require use of specific security layer for remote (RDP) connections (on Windows Server 2016)

   • Restrict Remote Desktop Services users to a single Remote Desktop Services session (on Windows Server 2012 or Windows Server 2008)

   • Restrict Terminal Services users to a single remote session (on Windows Server 2003)

   To enable the needed policy on Windows Server 2016

   To enable the needed policy on Windows Server 2016To enable the needed policy on Windows Server 2016

   1. In the tree on the left of the Group Policy editor, select Local Computer Policy > Computer Configuration > Administrative Templates > Windows Components.

   2. Then, select Remote Desktop Services > Remote Desktop Session Host > Security.

   3. In the Setting list on the right, double-click the Require use of specific security layer for remote (RDP) connections item.

   4. In the subsequent dialog, click Enabled.

   5. In the Security Layer drop-down list of the dialog, select Negotiate.

   6. Click OK to close the dialog and save the changes.

   To enable the needed policy on Windows Server 2008 and later

   To enable the needed policy on Windows Server 2008 and laterTo enable the needed policy on Windows Server 2008 and later

   1. In the tree on the left of the Group Policy editor, select Computer Configuration > Administrative Templates > Windows Components.

   2. Then select Remote Desktop Services > Remote Desktop Session Host > Connections.

   3. In the list on the right, double-click the Restrict Remote Desktop Services users to a single Remote Desktop Services session item.

   4. Click Enabled and click OK.

   To enable the needed policy on Windows Server 2003

   To enable the needed policy on Windows Server 2003To enable the needed policy on Windows Server 2003

   1. In the tree on the left of the Group Policy editor, select Computer Configuration > Administrative Templates > Windows Components.

   2. Then select Terminal Services.

   3. In the list on the right, double-click the Restrict Terminal Services users to a single remote session item.

   4. Click Enabled and click OK.

   If the node is running in Remote Administration Server mode and there are user sessions opened on it, close unnecessary sessions.

6. If the slave computer is configured to show a logon message when a user logs on, disable the message.

   To disable the message

   To disable the messageTo disable the message

   1. In the tree on the left of the Group Policy editor, select Configuration > Windows Settings > Security Settings > Local Policies > Security Options.

   2. In the list on the right, double-click the Interactive logon: Message title for users attempting to log on item.

   3. In the resulting dialog, set the title of the logon message to an empty string and click OK to save the changes.

   4. Then, right-click the Interactive logon: Message text for users attempting to log on item.

   5. Set the text of the logon message to an empty string and click OK.

   If the message persists

   If the message persistsIf the message persists

   1. On your slave computer, open the Registry editor (type regedit in the Search dialog and press Enter).

   2. Navigate to the following registry key:

      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

   3. Make sure that its LegalNoticeCaption and LegalNoticeText values are set to an empty string.

You can check whether the slave computer is configured correctly by connecting to it manually. If it does not show any additional messages or prompts, the group policies are configured correctly. Otherwise, you may need to ask your system administrator to disable those messages.

Sometimes, Windows is configured so that the user has to press Ctrl+Alt+Delete before signing in to prevent unwanted actions the software that simulates user behavior may perform. TestComplete does not provide any means to work around this feature, so we recommend you to turn it off. To do that:

1. On the target PC, press Win+R to open the Run dialog.

2. Type control userpasswords2 and press Enter.

3. In the subsequent User Accounts dialog, switch to the Advanced tab.

4. Unselect the Require users to press Ctrl+Alt+Delete option.

5. Click OK or Apply.

To avoid issues during the testing, make sure that, when you connect to the remote machine, its desktop opens up immediately – that is, no additional screens appear (such as the login form, account selection window, or RDP Certificate Warning windows). To learn how to disable these additional screens, contact your IT department.

If Jenkins or a Jenkins slave agent runs as a service under a non-interactive system account (for instance, Local System) on the computer where you run tests, TestComplete will also run under the non-interactive account. As a result –

• TestComplete will not have access to the user interface on the computer and will be unable to simulate user actions. Your automated tests that simulate user actions against GUI elements will fail.

• TestComplete will not be able to run tests in the CrossBrowserTesting cloud. The test step will fail.

If you connect to the slave computer using the Jenkins slave agent running as a Windows application (launched via Java Web Start), TestComplete will run under a user account and can interact with GUI elements.

If you connect to the slave computer using the Jenkins slave agent running as a Windows service, to avoid possible issues and allow TestComplete to interact with GUI elements:

1. Configure the Jenkins slave agent to run under the Local System account:

   

   Click the image to enlarge it.

2. Configure your TestComplete Test build steps in your Jenkins projects to open an interactive user session in which they will run. See the description of the Run interactive user session option of the TestComplete Tests build step or the description of the useTCService parameter of the step (for Pipeline script). If no interactive user session is open, your tests will fail.

   This feature is available only if you use TestComplete 10.60 or later. If you use TestComplete 10.50 or earlier, connect slave machines using the Launch slave agents via Java Web Start launch method.

On Windows 8 and later, TestComplete requires elevated permissions for the run. Jenkins that is run through the Java Web Start agent application, cannot start TestComplete with required permissions, and will cause the build step to fail if it tries.

To run tests under Windows 8 and later, do any of the following:

• Install the Java Web Start agent as a service. As a service, the agent has the required permissions and can start TestComplete. Make sure the "Run interactive user session" test step option is selected.

– or –

• Connect to the slave by using the "Let Jenkins control this Windows slave as a Windows service" launch method. Make sure the "Run interactive user session" test step option is selected.

– or –

• Disable support for testing Windows Store applications. With this option disabled, TestComplete can be run without elevated permissions.

In TestComplete, you can run web tests in testing environments provided by CrossBrowserTesting.com. To learn more, see Integration With CrossBrowserTesting.com.

To run tests in CrossBrowserTesting environments from your Jenkins nodes, the following requirements must be met:

• TestComplete must be installed on your Jenkins nodes. TestExecute cannot run tests in CrossBrowserTesting environments.

• The TestComplete version must be 12.20 or later.

• TestComplete on your Jenkins nodes must have an active license for the TestComplete Web module.

• You must have an active CrossBrowserTesting account.

• On your Jenkins nodes, provide valid account information for TestComplete to connect to the CrossBrowserTesting cloud.

  Connecting to CrossBrowserTesting.com from TestComplete

  Connecting to CrossBrowserTesting.com from TestCompleteConnecting to CrossBrowserTesting.com from TestComplete

  1. Log in to your Jenkins nodes using the Windows user account under which the tests will be run.

     TestComplete associates the CrossBrowserTesting account with your Windows account. So, it is important that you log in to your Jenkins nodes, set the CrossBrowserTesting account in TestComplete, and run the tests later under the same Windows account.

  2. Launch TestComplete.

  3. Open any project suite or create a new one.

  4. In the Project Explorer, locate the CrossBrowserTesting item. Double-click it to open.

  5. Click Sign In or Free Trial and then click Sign In to open the Sign In to Your Account dialog.

     In the dialog, enter your CrossBrowserTesting account credentials.

     TestComplete will save the credentials and will use them for all project suites you will run under your current Windows account.

  6. Close TestComplete and log off.

  To learn more, see Connecting to CrossBrowserTesting.com From TestComplete.

In addition, configure your test step to run TestComplete in an interactive user session under a user account (see below). Otherwise, the test step will fail.