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.

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.
  - Script Playback
    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.
  - Enabling the dynamic find feature in the Visual Studio IDE
    The HCL OneTest™ UI test object map lists the test objects in the application under test, in a hierarchy. Changes to the application under test might result in changes in object hierarchy. During playback, HCL OneTest UI is 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 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 scripts from HCL OneTest™ UI
    You can run scripts from HCL OneTest™ UI so that all of your recorded actions are played back. The recorded actions include the actions that you performed to start and stop an application, add verification points, and any other actions that you performed while using the application.
  - Playback of test scripts for HTML applications by using the Web UI engine
    You can play back test scripts for HTML applications in web browsers by using the Web UI engine without enabling the Java environments and browsers.
  - 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.

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.

You can run functional test scripts as part of your automated testing. See Script Playback. You can run scripts as part of any of the following test phases:

Prerequisites for functional test runs

You must have recorded test scripts in the Functional Test perspective of HCL OneTest™ UI. See Testing with Functional Test perspective.

Before you can configure a test run of a functional test, you must ensure that the application-under-test is in the same state that it was in when you recorded the script. See Restoring the test environment before playback.

You can configure how unexpected windows are to be handled so that scripts can be played back smoothly without interruption. See Configuring how to handle unexpected windows during playback.

If changes are made to the application-under-test after it was recorded, there might changes in the object hierarchy when you run such a test. You can avoid test failures by performing any of the following tasks:

Insert dynamic objects. See Inserting dynamic test objects.
Enable the dynamic find feature when you configure a test run. See Enabling the dynamic find feature.
Use ScriptAssure. See Using ScriptAssure.

If there are multiple instance of the applications under test, which might cause HCL OneTest™ UI to not identify the correct application, you can prevent or enable HCL OneTest™ UI to deal with this ambiguous recognition situation. See Ambiguous object recognition in functional testing.

Monitoring functional test runs

You can find information about monitoring test runs of a functional test:

You can use the playback monitor to view the test details as the test is played back. See Playback Monitor.
When you want to pause or stop the play back at any time after you started a run of the recorded script, you can pause or stop the test run. See Pausing or stopping script playback.

Running functional tests

You can find information about the following tasks that you can configure and run from the Functional Test perspective:

Analyzing test runs

After you run tests from the Functional Test perspective, you can perform the following tasks to debug or view the steps that failed in the test run: