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 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 Web UI test runs
See the different ways to play back Web UI tests.
Testing with Docker images
HCL OneTest™ UI, HCL OneTest Performance, and HCL OneTest Performance Agents are available for download as Docker images. You can use them to fulfill the continuous testing aspects of your DevOps lifecycle.
Running tests with containerized agents
When you have a local workbench, instead of installing the agents on different machines and locations, you can deploy the containerized agents to generate the load.

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 Web UI test runs
    See the different ways to play back Web UI tests.
    - Prerequisites to running Web UI tests
    - Running a Web UI test
      To verify that a web application works as designed, run the test in a browser. Optionally, you can run the test in more than one browser at a time to speed up your test effort. Before running the test, you can choose to use a specific browser profile for the test.
    - Running Web UI tests on BitBar Cloud
      You can run Web UI tests on mobile devices that are connected to the BitBar cloud device. After the test run is completed, you can view the test reports in HCL OneTest™ UI.
    - Running Web UI tests on BrowserStack Cloud
      You can run Web UI tests on the BrowserStack Cloud so that you can choose devices from a wide range of Android and iOS devices that are available for testing.
    - Running Web UI tests on the pCloudy cloud
      You can run Web UI test on Android or iOS devices that are connected to the pCloudy cloud testing platform. After the test run is completed, you can view the test reports in HCL OneTest™ UI.
    - Running Web UI tests on Perfecto mobile cloud
      You can run Web UI test on Android or iOS devices that are connected to the Perfecto mobile cloud testing platform. After the test run is completed, you can view the test reports in HCL OneTest™ UI.
    - Running a Web UI test by using industry-standard mobile browsers
      You can use industry-standard mobile browsers, such as Chrome and Safari, to run Web UI tests for mobile web applications. You can run tests with Chrome on Android devices and emulators and with Safari on iOS devices and simulators.
    - Running a test recorded in Google Chrome Device Mode
      You can run a test that you recorded in Chrome Device Mode. Doing so allows you to emulate the testing of applications on the browser of a mobile device.
    - Running tests in the headless mode
      When you do not want to view the GUI of the application under test as the recorded test is played back on a web browser, you can choose to run the test in the headless mode. Running of tests in the headless mode is useful when you use an automated testing environment.
    - Running tests in the private or incognito mode
      When you play back Web UI tests, if the user profile that is stored in the browser prevents the test from running without intervention, then you can use the private or incognito mode. Also, when you do not want cookies, caches, and user information to affect your test play back, you can choose the private mode.
    - Testing with Docker images
      HCL OneTest™ UI, HCL OneTest Performance, and HCL OneTest Performance Agents are available for download as Docker images. You can use them to fulfill the continuous testing aspects of your DevOps lifecycle.
      - Configuring Docker containers
        You can now deploy and configure the Docker containers on any computer and quickly get started with testing. You can push the product images to the Docker container to automate the playing back of tests.
      - Running tests with containerized agents
        When you have a local workbench, instead of installing the agents on different machines and locations, you can deploy the containerized agents to generate the load.
      - Running tests in a containerized workbench
        You can run tests in a containerized workbench after you deploy your Docker images. You need not install the workbench on your computer to run your tests.
      - Running an AFT suite in a containerized workbench and agents by using Docker Compose
        You can run an Accelerated Functional Test (AFT) suite in a containerized workbench and agents after you deploy your Docker images. You can use the Docker Compose tool to run an AFT suite and need not install the workbench or the agents on different computers.
  - Configuration of mobile test runs
    After you record the tests for mobile applications by using HCL OneTest™ UI, you can play back the recorded tests by using HCL OneTest UI. The test reports help you to analyze the functional and performance issues in the mobile applications developed.
  - Configuration of Windows test runs
    You can run Windows tests that you created for Windows desktop applications in HCL OneTest™ UI.
  - Configuration of AFT Suite runs
    When you create Web UI, mobile, or Windows tests, you must configure the play back of the recorded tests as AFT Suite runs before you can view their test results.
  - Running a test on multiple browsers and devices simultaneously
    Rather than run a Web UI test on one browser at a time, you can run a single Web UI test on multiple browsers simultaneously. Doing so can significantly speed up your test effort. You can also extend your test coverage by adding mobile devices to the test run. You can run the test from HCL OneTest™ UI, from the command line, or from Rational® Quality Manager. This topic describes how to run a test from the UI Test perspective.
  - Setting a global delay for test steps
    You can set the duration of a global delay in milliseconds between all the steps instead of adding the wait time manually for each of the steps in a recorded test. You can specify this global delay as a preference for the playback of Web UI, Windows, or mobile tests.
  - Configuration of test runs from the command line
    When you need to run Web UI, mobile, and windows tests using the command line without opening the desktop client to run these tests, you can use the command line of HCL OneTest™ UI.
- 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 tests with containerized agents

When you have a local workbench, instead of installing the agents on different machines and locations, you can deploy the containerized agents to generate the load.

Before you begin

You must have configured the Docker container. See Configuring Docker containers.

About this task

Typically, when the agents are installed, you specify the workbench host name and port number to establish the connection with the workbench. But containerized agents are already installed. Therefore, you specify the connection information during the run.

Note: The version number of the container images and the desktop products must match. If you have previous version of the container image, uninstall it, and then install the latest version.

To uninstall the image, you must stop the container by running the docker stop "CONTAINER ID" command, and then run the docker rmi -f "image ID" command to uninstall the image.

Procedure

Start the container instance of the agent by running the following command:

$ docker run -dit --rm -e MASTER_NAME=Workbench_name or IP -e MASTER_PORT=port_number -e AGENT_NAME=Agent_name -e AGENT_IP=IP_address imageName:imageVersion

Table 1. Description of parameters
Command	Description
-dit	Specifies that the agent container runs in the background.
--rm	Specifies to clean up the container and remove the file system when the container exits.
MASTER_NAME	Specifies the IP or host name of the workbench.
MASTER_PORT	Specifies the port number of the workbench. If you use the default port number of 7080, this command is optional.
AGENT_NAME	Optional: Specifies the name of the agent that report to the workbench.
AGENT_IP	Optional: Specifies the IP address of the agent that report to the workbench.
imageName:imageVersion	Specifies the name and version of the image.

Select the Web UI tests to run from the UI Test perspective, and then click Run Distributed Tests from the context menu.

The tests are distributed among the connected agents.