Known Issues

Applies to TestComplete 14.73, last modified on February 25, 2021

In TestComplete 14.40, you can create cross-platform web tests. These tests are created on a local computer and then run in multiple remote environments managed by Selenium Grid. When running your web tests in remote environments, you may encounter the following issues:

  • TestComplete may fail to access the CrossBrowserTesting.com device cloud when connecting to it from a computer running under the Windows 7 operating system. This can happen if the Windows update that sets TLS as the default security protocol is not installed on that computer. To resolve the issue, install the update. You can find information on the update and instructions on how to install it at support.microsoft.com/en-us/help/3140245/update-to-enable-tls-1-1-and-tls-1-2-as-default-secure-protocols-in-wi.

  • In Internet Explorer, TestComplete may fail to record cross-platform tests if web elements in your tested web application have dynamic IDs, and the application’s object hierarchy has many levels. To avoid the issue, record your cross-platform web tests in any other supported web browser (which one it will be does not matter as the resulting test will be browser-independent).

  • In Internet Explorer, TestComplete may fail to simulate clicks that do not rely on coordinates. To avoid possible issues, you can do the following:

  • If the compatibility mode is enabled in Internet Explorer, TestComplete will not be able to record cross-platform web tests in it. To disable the compatibility mode in Internet Explorer:

    1. In the web browser, select the Tools > Compatibility View settings.

    2. In Internet Explorer 11, clear the Display intranet sites in Compatibility View check box.

      In Internet Explorer 10, clear the Display all websites in Compatibility View and Display intranet sites in Compatibility View check boxes.

    In addition, we recommend that you use Google Chrome or Firefox to record cross-platform web tests instead of Internet Explorer.

  • In the mobile version of Safari, TestComplete may fail to simulate coordinate-based clicks. To avoid possible issues, you can do the following:

    • Simulate clicks without specifying the target coordinates. In this case, TestComplete will simulate the action at the center of the target control. To learn more, see the appropriate click method description.

    • Run your test in another web browser.

  • On images captured by Test Visualizer in iOS Safari, the red frame highlighting the tested object may be misplaced.

  • In Chrome, on Android devices, your tests may fail to simulate coordinate-based clicks. To avoid possible issues, you can do the following:

    • Simulate clicks without specifying the target coordinates. In this case, TestComplete will simulate the action in the center of the target control. To learn more, see the appropriate click method description.

    • Run your test in another web browser or on another mobile device.

  • In Chrome, on Android devices, your tests may simulate non-coordinate-based clicks at an incorrect target point. If you face such an issue, you may do the following:

    • Run your test in another web browser or on another mobile device.

    • Specify the coordinates at which the click is to be simulated explicitly. This is not recommended as clicks at specific coordinates may fail in Chrome on some Android devices (see above).

  • When running tests in headless Chrome, TestComplete cannot maximize the browser window. Both the BrowserWindow.Maximize method and launching the browser with the --start-maximized command line will be ineffective. This may cause your tests to fail to simulate user actions over controls that are not visible in the browser window.

    To avoid possible problems, you can use the goog:chromeOptions capability to set the web browser window size explicitly by using the --window-size command-line parameter. For example:

    var capabilities =
      {
      "browserName": "chrome",
      "goog:chromeOptions": {
        "args":
          ["--headless",
          "--window-size=1920x1080"
        ]
      }
    }

  • In the headless version of Firefox, methods that navigate to a web page (for example, the RemoteItem.Run, RemoteItem.Navigate, Page.ToUrl, Page.NavigateTo, Browser.Navigate methods) may fail.

  • Your tests may fail to simulate drag actions, or the web browser where the test is running may stop responding when the drag action is being simulated. For instance:

    • Chrome may stop responding.

    • In Firefox, a click on the target point may be simulated instead of the drag action.

    • In Safari, the drag action may be simulated in an incorrect direction or within an incorrect distance.

  • On mobile devices, methods that modify the browser window size or position, for example, BrowserWindow.Position or BrowserWindow.Maximize, will fail. This happens because on mobile devices the web browser is always in the fullscreen mode.

  • On mobile devices, simulating user actions over date interface of date input controls (<input type="date">) is not supported. Setting a control’s date by simulating key input with the Keys or SetText methods is not supported either.

    In your tests, set the date directly by assigning it to the value property of the control. For example:

    page.FindElement("input").value = "2020-12-31";

    Notes:

    • Set the date in the yyyy-mm-dd format regardless of the date display format.

    • If you have a test operation that simulates a click over the date picker control right before you set its date, we recommend that you disable that operation. Otherwise, the control's date interface might overlap the control and disrupt further testing.

  • When setting the browser window position with the BrowserWindow.Position method, the resulting window size may differ from the intended size specified by the method parameters. This happens because of the known WebDriver limitation. You can find more information at www.w3.org/TR/webdriver/#set-window-rect.

  • If your Selenium Grid node uses an obsolete version of WebDriver (non-compliant with the recent WebDriver specification version), your tests may fail to simulate mouse actions (for example, clicks, drags, hovers, and so on) over web pages and the web browser window on the node.

See Also

About Cross-Platform Web Tests

Highlight search results