Welcome
Troubleshooting
This guide describes how to analyze and resolve some of the common problems that you might encounter while you work with HCL DevOps Test UI (Test UI).
Troubleshooting in the Functional Test perspective
In this section, you will learn how to troubleshoot the tests in the Functional Test perspective.
Collecting DevOps Test UI error logs
While working with HCL DevOps Test UI (Test UI), you might encounter some problems that you can easily troubleshoot.

Release Notes
This document includes information about the new features introduced, features deprecated or removed, defects fixed, and known issues identified in this version of HCL DevOps Test UI (Test UI). You can also find the installation and upgrade instructions along with the contact information of HCL Customer Support.
System Requirements
This document includes information about hardware and software requirements for HCL DevOps Test UI (Test UI) 2024.03 (11.0.1).
Getting Started Guide
This guide provides an overview of HCL DevOps Test UI (Test UI). You can find the task flows to get you started with Test UI. This guide is intended for new users.
Tutorials
You can learn to start using Test UI by reviewing the information in the Tutorials for the UI Test perspective and Functional Test perspective.
Samples
You can find the sample project that you can use with HCL DevOps Test UI (Test UI) to test the functionality of an application.
Administrator Guide
This guide describes how to install HCL DevOps Test UI (Test UI) software. After you install the software, you can perform administration tasks such as license configuration and integration with other products. This guide is intended for administrators.
Test Author Guide
This guide describes how to create test scripts and enhances them by applying different test elements such as dataset, variables, and verification points.
Test Execution Specialist Guide
This guide describes how to automate the playback of the tests by using different methods such as Docker, IBM Cloud Private, Jenkins and so on. The test results can be pushed to HCL DevOps Test Virtualization Control Panel (Test Virtualization Control Panel).
Test Manager Guide
This guide describes how to keep track of the performance of the application by evaluating the test results. Following topics cover how you can work with the test results.
Troubleshooting
This guide describes how to analyze and resolve some of the common problems that you might encounter while you work with HCL DevOps Test UI (Test UI).
- Troubleshooting in the UI Test perspective
  You can find information about the issues or problems that you might encounter while working with HCL DevOps Test UI (Test 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.
- Troubleshooting in the Functional Test perspective
  In this section, you will learn how to troubleshoot the tests in the Functional Test perspective.
  - Troubleshooting functional tests in Mozilla Firefox browsers
    If you encounter problems while testing in Mozilla Firefox browsers, the following workarounds might help resolve them.
  - Troubleshooting functional tests in the Google Chrome browser
    If you encounter problems while testing in the Google Chrome browser, you will find useful information in this section to resolve them.
  - Unable to test eclipse-based applications
    Generally the applications that are enabled for functional testing is in the enabled state after you upgrade HCL DevOps Test UI (Test UI). If you find any issues while testing the applications, disable the Eclipse application and enable it again for functional testing.
  - Ambiguous object recognition in functional testing
    Ambiguous recognition occurs when HCL DevOps Test UI (Test UI) can not uniquely identify an object in the system-under-test. This commonly happens when Test UI cannot differentiate between an instance of the application-under-test started by a script playback and an instance of the same application inadvertently left open previous to script playback. This also applies to identical windows from one application and identical HTML documents. Ambiguous recognition will cause script playback failure unless the duplicate application is closed.
  - Screen snapshot on playback failure of functional tests
    If playback of a script causes an exception to be thrown, HCL DevOps Test UI (Test UI) takes a screen snapshot at the time of the failure. The screen snapshot is accessible through the log.
  - Tips and tricks for functional testing HTML applications
    This topic provides tips and tricks for recording and playing back scripts to test HTML applications.
  - Unable to record tests with the simplified scripting preference
    When you record tests for an HTML application, the recording window of the functional test script either does not capture test steps or slows down if you selected Enable Simplified Scripting in the Preferences window for Functional Testing.
  - Java applets in HTML pages
    You can test Java™ applets within a browser (Firefox, Internet Explorer). Java applets are not mapped as nested within HTML but are recorded as top-level objects. In the test object map, applets appear at the top level.
  - Standard properties available for functional testing HTML objects
    Standard properties provide a common way to access properties and their values across browsers. This topic lists the standard properties available for HTML objects.
  - Uninstalling DevOps Test UI cleanly
    If you have any issues during uninstall and reinstall of HCL DevOps Test UI (Test UI), you can perform a few tasks to verify whether the required processes are stopped and all the files are deleted from the computer.
  - Problems with object recognition
    If you encounter a problem with object recognition during testing, you might be able to resolve the problem by following these instructions.
  - Unable to find the correct control by using the Insert Test Object option
    When you try to add a step in the functional test script by using the Insert Test Object option, HCL DevOps Test UI (Test UI) fails to find the correct control.
  - Unable to create a verification point by using the vpDynamic action
    When you run a functional test for the first time to create a verification point by using the vpDynamic("vpName").performTest() action in the test script, the test step fails.
  - Playback fails for functional tests with startApp(param1, param2)
    When you run a functional test for an HTML application by using the Web UI engine that has a test step with startApp(executable, url) to open the application, then HCL DevOps Test UI (Test UI) switches to any active window that is maximized and the test fails.
  - Unable to locate the dataset in a compound test
    When you play back a compound test that contains a functional test script associated with a dataset, the playback fails.
  - Troubleshooting issues in SAP tests
    You can find information about the issues or problems that you might encounter while you test the SAP GUI. Details about issues, their causes and the resolutions that you can apply to fix the issues are described in the following table.
  - Problems with environment enablement
    When it is not possible to record on the application-under-test, you must verify whether the test environment was enabled for functional testing.
  - Handling exceptions
    If an exception occurs during testing, you might be able to handle it by following these instructions. Two common exceptions are the ambiguous recognition exception and the Mutex timeout exception during playback.
  - Collecting DevOps Test UI error logs
    While working with HCL DevOps Test UI (Test UI), you might encounter some problems that you can easily troubleshoot.
  - Viewing trace files within DevOps Test UI
    You can view HCL DevOps Test UI (Test UI) trace files in the Test UI integrated development environment (IDE) Error Log view.
  - AutoPD Collection artifacts in IBM® Support Assistant
    HCL DevOps Test UI (Test UI), contributes a few files that the Automated Problem Determination (AutoPD) Collector tool in the IBM® Support Assistant application uses.
  - Unable to play back tests when the computer is locked
    The functional test script fails to identify the correct control and the playback fails if your computer is locked during the playback.
  - Frequently asked questions
    This section provides answers to frequently asked questions about HCL DevOps Test UI (Test UI).
  - Error messages
    This section provides information about error messages that you might encounter with HCL DevOps Test UI (Test UI). This section lists the error messages by ID, explanation, system action and your response to correct the error message.
Reference Guide
This guide describes the additional topics to gain more knowledge about HCL DevOps Test UI (Test UI).
All Guides (PDF)
You can find the link to view or download the content of the release notes, system requirements, and persona guides of HCL DevOps Test UI (Test UI) as a PDF file.
Security Considerations
You can take certain actions to ensure that your installation is secure, customize your security settings, and set up user access controls.
Notices
This document provides information about copyright, trademarks, terms and conditions for the product documentation.

Collecting DevOps Test UI error logs

While working with HCL DevOps Test UI (Test UI), you might encounter some problems that you can easily troubleshoot.

About this task

To generate Test UI error logs:

Procedure

Set the preferences for logging and tracing in the Logging and Tracing page. Click Window > Preferences, expand Functional Test in the left pane, and then click Logging and Tracing. You can collect the errors, warning, and information messages into a log file (rft_log.txt). The debug information is collected as trace date into the trace file. The trace file can be either a .txt file or a .log file, depending on your specification in the Logging and Tracing page. Trace files in the .log format can be imported into the Eclipse Error Log view within Test UI for viewing and filtering. You can specify the log file and the trace file directory.
Perform the operation that caused the problem.