Welcome
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).
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 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 DevOps Test UI (Test UI).
Running Web UI tests in the private mode from the command line
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 from the command line. Also, when you do not want cookies and caches to affect your test play back, you can choose the private mode.

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.06 (11.0.2).
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).
- 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.
  - Configuration of mobile test runs
    After you record the tests for mobile applications by using HCL DevOps Test UI (Test UI), you can play back the recorded tests by using Test 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 DevOps Test UI (Test 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 DevOps Test UI (Test UI), from the command line, or from Engineering Test Management. 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 DevOps Test UI (Test UI).
    - Running a test from the command line
      You can run Web UI, mobile, and windows tests using the command-line interface of HCL DevOps Test UI (Test UI).
    - Running multiple tests from the command line
      When you want to run multiple tests or compound tests that are in a project folder, you can select and run those tests by using any of the command options such as "*" or testType from the command line.
    - Creating a command-line config file
      Starting from 10.0.2, you can create command line config file from the product, which you can use while running tests from the command-line interface and Maven.
    - Running Web UI tests from the command-line
      You can run a Web UI test without using the desktop client by using the command-line interface. You must use the -varfile parameter that specifies the complete path to the XML file in the command. The XML file contains the name-value pairs of the variables. The variables file specifies the web browser on a computer, device, emulator, or device on a cloud on which to run the test.
    - Running a Web UI test or compound test in the headless mode from the command line
      When you do not want to view the GUI as the recorded test is played back on a web browser, you can choose to run the test in the headless mode from the command line. Running of tests in the headless mode is useful when you use an automated testing environment.
    - Running Web UI tests in the private mode from the command line
      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 from the command line. Also, when you do not want cookies and caches to affect your test play back, you can choose the private mode.
    - Running tests by using the browser launch arguments from the command line
      You can open the browser with specific browser launch arguments when you play back Web UI tests through the command line. You can specify the required arguments through a variable file.
    - Running a test from the command line on multiple browsers
      In addition to running a Web UI test from the product interface, you can automate the test effort by running the test from the command line. To accelerate test execution, you can run a single Web UI test and/or a compound test containing Web UI tests on multiple browsers and devices simultaneously.
    - Running multiple tests simultaneously from the command line
      You can use an XML file and the command line to run multiple Web UI tests and compound tests simultaneously on instances of Chrome and Firefox. You can also distribute these tests across multiple remote agent computers. Starting from 9.1.1.1, this feature is also available from the command line.
    - Running mobile tests for Android applications from the command-line
      You can run a mobile test without using the desktop client by using the command-line interface. You must use the -varfile parameter that specifies the complete path to the XML file in the command. The XML file contains the name-value pairs of the variables. The variables specify the path to the computer to which the Android device or emulator is connected, and the other configurations required to run the mobile test on the connected device.
    - Running mobile tests for iOS applications from the command-line
      You can run a mobile test without using the desktop client by using the command-line interface. You must use the -varfile parameter that specifies the complete path to the XML file in the command. The XML file contains the name-value pairs of the variables. The variables specify the path to the computer to which the iOS device or simulator is connected, and the other configurations required to run the mobile test on the connected device.
    - Running Windows tests from the command-line interface
      You can run a Windows test without using the desktop client by using the command-line interface. You can either run the Windows test on the local computer or on a remote computer.
- 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 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).
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.

Running Web UI tests in the private mode from the command line

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 from the command line. Also, when you do not want cookies and caches to affect your test play back, you can choose the private mode.

Before you begin

You must have completed the following tasks:

Recorded a Web UI test to run in the private mode.
Read and been familiar with the command line arguments to use with the cmdline command. See Configuration of test runs from the command line.
Read and been familiar with the usage of variable files. See Using a variable file.

Procedure

Create a variable file with the following variable name and its value:

<variable_init name="<browser_name>.private" value="true" />

Use the following values for the specific browser:


Browser	Value
Chrome	<variable_init name="chrome.private" value="true" />
Edge	<variable_init name="edge.private" value="true" />
Firefox	<variable_init name="firefox.private" value="true" />
Opera	<variable_init name="opera.private" value="true" />

The sample variable file for running a test in the private mode of Chrome browser is as follows:

<?xml version="1.1" encoding="UTF-8"?> 
<inits xmlns="http://www.ibm.com/rational/test/lt/varinit"> 
    <variable_init name="chrome.private" 
        value="true" /> 
</inits>

Go to one of the following directories:
- <productInstallationDirectory>\cmdline directory that contains cmdline.sh on the Linux operating system.
- <productInstallationDirectory>\cmdline directory that contains cmdline.sh on the Mac operating system.
- <productInstallationDirectory>\cmdline directory that contains cmdline.bat on the Windows operating system.
Close Test UI, if it is open, before you run the cmdline command.
Enter the following command to run the test in the private mode:
cmdline -workspace <workspacename> -project <projectname> -suite <suitename> -varfile <variable_file_full_path>
For example:
```
cmdline -workspace D:\My Workspace -project myProject -suite Tests\myWebUITest.testsuite -varfile "D:\My Workspace\priv.varinit"
```
The test run starts and the status is displayed on the screen.

Results

You have run the test in the private mode from the command line.