Welcome
Test Execution Specialist guide
A test executor automates 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 Quality Server.
Running tests from Functional Test perspective
In this section, you will learn how to play back tests from the Functional Test perspective.
Running a script from the Microsoft™ Edge browser
You can use HCL OneTest™ UI to play back test scripts using the Microsoft™ Edge browser.

Release Notes
This document contains information about new features, system requirements, and known limitations in HCL OneTest™ UI.
System Requirements
This document includes information about hardware and software requirements for HCL OneTest™ UI.
Getting Started Guide
This guide provides an overview of HCL OneTest™ UI. You can find the task flows to get you started with HCL OneTest UI. This guide is intended for new users.
Tutorials
This section contains the tutorials which explains the main features of HCL OneTest™ UI.
Samples
This section describes about the sample project which can be used with HCL OneTest™ UI to test the functionality of an application.
Administrator guide
Typically, a user with the administrator role is responsible for certain tasks including installation, configuration, and integration of the product. This guide lists all such topics.
Test Author guide
As a test author, you are responsible to create test scripts and enhances them by applying different test elements such as dataset, variables, and verification points.
Test Execution Specialist guide
A test executor automates 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 Quality Server.
- Running tests from Web UI Test perspective
  In this section, you will learn how to play back tests from the Web UI Test perspective.
- Running tests from Functional Test perspective
  In this section, you will learn how to play back tests from the Functional Test perspective.
  - Running scripts
    When you play back a script, HCL OneTest™ UI replays your recorded actions, which automates the software testing cycle.
  - Restoring the test environment before playback
    The state of both the environment and the application-under-test can affect script playback. If the recorded environment and the playback environment are different, playback problems can occur.
  - Configuring how to handle unexpected windows during playback
    Problems can occur during script playback if unexpected windows are displayed. Unexpected windows such as security and warning message dialog boxes or custom dialog boxes can cause playback failure with exceptions such as object not found or window not activated. You can configure how unexpected windows can be handled so that scripts can be played back smoothly without interruption.
  - Inserting dynamic test objects
    You can also insert dynamic test objects by using Insert Dynamic Test Object. The hierarchy of a test object in the object map represents the order of search of the particular control during playback. Over a series of application changes, the hierarchy of the objects may change if new objects are introduced in the test application. This results in a playback failure. Using dynamic test objects you can anchor a test object as a descendant to its parent.
  - Enabling the dynamic find feature
    The test object map lists in a hierarchy the test objects in the application under test. Changes to the application-under-test might result in changes in the object hierarchy. During playback, HCL OneTest™ UI is then unable to find an object whose hierarchical position has changed, and this causes playback failure. With the dynamic find feature you can prevent playback failure that results from hierarchy changes in the application under test. The dynamic find feature performs searches for objects whose hierarchy has changed, when a search that is based on object recognition scoring (ScriptAssure) fails to find such objects.
  - Using ScriptAssure
    Using ScriptAssure™, you can play back scripts successfully even when the application-under-test has been updated.
  - Ambiguous object recognition in functional testing
    Ambiguous recognition occurs when HCL OneTest™ UI can not uniquely identify an object in the system-under-test. This commonly happens when HCL OneTest 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.
  - Playback Monitor
    During playback you can view the script name, the number of the line that is executing, status icons, and a description of the action in progress from the Playback Monitor.
  - Pausing or stopping script playback
    Playback of a script can be paused or stopped.
  - Running a script from HCL OneTest™ UI
    When you run a script from HCL OneTest™ UI, it plays back all of your recorded actions, such as starting an application, the actions you take in the application, verification points, and stopping the application.
  - Running Functional tests for HTML applications by using the Web UI extension
    When you want to run Functional tests for HTML applications in Google Chrome, Microsoft Edge and Firefox browsers without enabling the browsers and Java environments, you can do so by using the Web UI extension.
  - Running a script from the Microsoft™ Edge browser
    You can use HCL OneTest™ UI to play back test scripts using the Microsoft™ Edge browser.
  - Debugging scripts
    You can use the same process to debug a Functional Test script as you would to debug other Visual Basic or Java™ applications. If you prefer, in HCL OneTest™ UI, Eclipse Integration, you can debug your script in the HCL OneTest UI Debug Perspective which makes it easier to start the debugger that comes with the Java Development Toolkit.
  - Screen snapshot on playback failure of functional tests
    If playback of a script causes an exception to be thrown, HCL OneTest™ UI takes a screen snapshot at the time of the failure. The screen snapshot is accessible through the log.
Test Manager guide
As a test manager, you can 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
While working with HCL OneTest™ UI, you might encounter some problems that you can easily troubleshoot. The topics in this section address some of these problems.
Reference
Use these additional topics to gain more knowledge about the product.
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 OneTest™ 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.

Running a script from the Microsoft™ Edge browser

You can use HCL OneTest™ UI to play back test scripts using the Microsoft™ Edge browser.

Before you begin

Verify that Microsoft™ Edge browser v40.15063.0.0 or later is installed on your system. To check the version:

Start Microsoft™ Edge.
Click the More (…) menu.
Select Settings, and then scroll down to the bottom.

Procedure

To automatically install the Microsoft™ WebDriver for Edge 44, run the following command in the elevated command prompt: DISM.exe /Online /Add-Capability /CapabilityName:Microsoft.WebDriver~~~~0.0.1.0.

Note: To install WebDriver for Edge 42 and earlier, download and install the latest version of Microsoft WebDriver server in the default location for both 32-bit and 64-bit Windows 10 computers. See https://developer.microsoft.com/en-us/microsoft-edge/tools/webdriver.
For Edge 42 and earlier, you must set the environment variable webdriver.edge.driver with the full path to the installation file named MicrosoftWebDriver.exe.
1. In the Control Panel, click System > Advanced system settings > Advanced > Environment variables.
2. In System Variables, click New, and in Variable name, enter webdriver.edge.driver.
3. In the Variable value field, enter the path to the MicrosoftWebDriver.exe and click OK.
  
  Note: You need not manually set environment variable for Edge 44.
Open the ivory.properties file in <SDP_DIRECTORY>\FunctionalTester\bin\ and change the line #rational.test.ft.timeout_pb_event_consumed=1000 to rational.test.ft.timeout_pb_event_consumed=0.

Note: You must remove # and change 1000 to 0.
Restart HCL OneTest™ UI.
Start the Edge browser using either startBrowser() or startApp().
- To use startBrowser(): startBrowser("Edge", "https://www.google.co.in/");
- To use startApp():
  1. ClickConfigure > Enable Environments for Testing > Web Browsers and click Add.
  2. Browse to C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe and click Add.
  3. Add an HTML application and select Edge as the browser in the Configure > Configure Applications for Testing wizard.
Add sleep() of at least 15 seconds after startBrowser() or startApp().