Home
Troubleshooting
This guide describes how to analyze and resolve some of the common problems that you might encounter while you work with HCL OneTest™ UI.
Troubleshooting in the UI Test perspective
You can find information about the issues or problems that you might encounter while working with HCL OneTest™ UI in the UI Test perspective. Details about issues, their causes and the resolutions that you can apply to fix the issues are described in this section.
The AUT displays the 403 forbidden error
When you record or play back a Web UI test, the application under test (AUT) fails to open and displays the 403 forbidden error.

Troubleshooting
This guide describes how to analyze and resolve some of the common problems that you might encounter while you work with HCL OneTest™ UI.
- Troubleshooting in the UI Test perspective
  You can find information about the issues or problems that you might encounter while working with HCL OneTest™ UI in the UI Test perspective. Details about issues, their causes and the resolutions that you can apply to fix the issues are described in this section.
  - Unable to play back Web UI tests when certain web applications are redirected to a different URL
    When you record a Web UI test and enter the URL of the web application that you want to test, the application might be redirected to a different URL. When you play back this recorded Web UI test, the playback fails.
  - Unable to open a browser for the Web UI test playback
    When you play back a Web UI test, the test fails occasionally before HCL OneTest™ UI opens a browser.
  - The AUT displays the 403 forbidden error
    When you record or play back a Web UI test, the application under test (AUT) fails to open and displays the 403 forbidden error.
  - Unable to verify content in a Windows test
    When you play back a Windows test with a content verification point, the test fails to verify the text content.
  - Unable to run Web UI tests on a remote agent on Linux
    When you run Web UI tests on a remote agent that runs on Linux, the browser fails to launch.
  - Unable to record or run Web UI tests on Chrome 111 or Edge 112
    When HCL OneTest™ UI opens Google Chrome 111 or Microsoft Edge 112 to record or play back a Web UI test, the browser opens with a blank page and fails to record or run the test.
  - Unable to run Web UI tests on an Android 13 device or emulator
    When you run Web UI tests in Google Chrome versions that are earlier than 110 on an Android 13 device or emulator, the browser fails to open.
  - Unable to generate tests in a Linux or Mac operating system
    When you install HCL OneTest™ UI on a Linux or Mac operating system and create a test, occasionally, the test generation fails with NullPointerException.
  - HCL OneTest™ UI error messages
    This section provides information about error messages that you might encounter with HCL OneTest™ UI. This section lists the error messages by ID, explanation, system action and your response to correct the error message.
  - Frequently Asked Questions
    This document answers some of the common queries in mobile testing.
- Troubleshooting in the Functional Test perspective
  In this section, you will learn how to troubleshoot the tests in the Functional Test perspective.

The AUT displays the 403 forbidden error

When you record or play back a Web UI test, the application under test (AUT) fails to open and displays the 403 forbidden error.

Cause

The Web UI testing fails because access to the web page is forbidden in the browser instance that is opened for test run.

Resolution

Follow these steps in the New Test From Recording wizard to fix the 403 forbidden error while you record the test in a browser:
1. Select the options for the Web UI test in the Recording Session screen.
2. Click Next.
  The Select Location page is displayed.
3. Specify the name and location for the test, and then click Next.
  The Select Client Application page is displayed.
4. Select a browser, and then click Next.
  The Recorder Settings dialog is displayed.
5. Select the Web UI recording > Launch browser with arguments option in the Advanced section to specify the argument to be used when HCL OneTest™ UI opens the browser.
6. Enter the following argument in the text box:
```
--disable-blink-features=AutomationControlled
```
7. Click Finish.
Follow these steps in the Run Configuration dialog to fix the 403 forbidden error while you play back the test in a browser:
1. Select the options as required for the test run in the Run Configuration page.
2. Click Next.
  The Advanced playback options page is displayed.
3. Select the Launch browser with arguments checkbox to specify the argument to be used when HCL OneTest™ UI opens the browser.
4. Enter the following argument in the text box:
```
--disable-blink-features=AutomationControlled
```
5. Click Finish.