Home
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® Quality Server.
Configuration of test runs from the Functional Test perspective
When you created functional tests, you must configure the run of the recorded functional tests from the Functional Test perspective before you can view the test results.
Running functional tests for HTML applications by using the Web UI engine
When you want to run functional tests for HTML applications in browsers without enabling the Java environments and browsers, you can do so by using the Web UI engine.

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® Quality Server.
- Configuration of test runs from the UI Test perspective
  When you create Web UI, mobile, or Windows tests, you must configure the play back of the recorded tests as test runs from the UI Test perspective before you can view their test results.
- Configuration of test runs from the Functional Test perspective
  When you created functional tests, you must configure the run of the recorded functional tests from the Functional Test perspective before you can view the test results.
  - 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
    You can run test scripts from HCL OneTest™ UI to play back all your recorded actions. The playback of the recording can include the actions that you performed to start and stop an application, to add verification points, and the actions you performed while using the application.
  - Running functional tests for HTML applications by using the Web UI engine
    When you want to run functional tests for HTML applications in browsers without enabling the Java environments and browsers, you can do so by using the Web UI engine.
  - 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.

Running functional tests for HTML applications by using the Web UI engine

When you want to run functional tests for HTML applications in browsers without enabling the Java environments and browsers, you can do so by using the Web UI engine.

About this task

To run functional tests for the HTML applications in web browsers, you must first enable the Web UI engine for the functional test from the Preferences menu.

You can also configure HCL OneTest™ UI to select a specific browser profile that you configured to add the home page, extensions, and settings for the browser to run the tests. You can select the profile in Preferences by going to Window > Preferences > Test > Test Execution > UI Test Playback > Browser. For more information, see the related information.

If you select a specific profile for the browser, the browser displays the details that are set for the profile before the actual Application Under Test (AUT) is loaded.

If you do not select a specific profile for the browser, the test runs on the browser with a temporary profile, which is not configured with any predefined settings.

Procedure

Enable the Web UI extension from the Functional Test perspective by performing the following steps:
1. Go to Windows> Preferences> Functional Test> Playback menu.
  
  The Playback settings page is displayed.
2. Select the following checkboxes:
  - Play back with Web UI Extension
  - Play back with Web UI action
3. Click Apply.
Run the functional test.
Notes:
- When you run the functional test for any HTML application in the Mozilla Firefox, Microsoft Edge, or Google Chrome browser by using the Web UI engine, and if there is a browser and driver incompatibility, HCL OneTest™ UI automatically downloads the appropriate driver to play back tests successfully.
- You can clear the cache and history of the Mozilla Firefox, Microsoft Edge, and Google Chrome browsers by selecting certain checkboxes in the Preferences menu. You can select the Clear cache and Clear history checkboxes by going to Window > Preferences > Test > Test Execution > UI Test Playback > Desktop.

Results

You have run functional tests for HTML applications by using the Web UI engine.