Welcome
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.
Tests in the Functional Test perspective
When you develop Java, HTML, or Terminal-based applications, you can use HCL DevOps Test UI (Test UI) to create traditional functional tests for these applications. You must first record the tests and then use Test UI to run the tests before you can view the test results.
Functional tests with external data
You can use external data to data-drive functional tests. When you data-drive a test, the script uses variables for key application input fields and programs instead of literal values so that you can use external data as you data-drive the application you are testing.
Creating a dataset
A dataset is a collection of related data records which supplies realistic data values to the variables in a test script during test script playback. You can create data from scratch or import existing data into a new dataset from another dataset or a .csv file.

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.
- Tests in the UI Test perspective
  When you develop web applications, Windows-based applications, or mobile applications, you can use HCL DevOps Test UI (Test UI) to create functional tests for these applications. You must first record the tests and then use Test UI to run the tests before you can view the test results.
- Tests in the Functional Test perspective
  When you develop Java, HTML, or Terminal-based applications, you can use HCL DevOps Test UI (Test UI) to create traditional functional tests for these applications. You must first record the tests and then use Test UI to run the tests before you can view the test results.
  - Preparing the functional test environment
    This section describes the tasks you must perform to configure the functional test environment.
  - Functional test assets
    This section describes the different types of functional test assets that are available in HCL DevOps Test UI (Test UI).
  - Functional test projects
    A functional test project stores application test assets such as scripts, object maps, verification point baseline files, and script templates. You must create a functional test project before you can record scripts.
  - Working with functional test scripts (Windows-only)
    This section describes the process of creating functional test scripts to test your applications.
  - Verification points
    Verification points verify whether an expected behavior occurred during a test playback, or they verify whether there is a change in the state of a control or an object. When you create a verification point, you capture information about a control or an object in the application to establish this information as a baseline for comparison during the playback.
  - Functional tests with external data
    You can use external data to data-drive functional tests. When you data-drive a test, the script uses variables for key application input fields and programs instead of literal values so that you can use external data as you data-drive the application you are testing.
    - Data-driving functional tests
      To data-drive a test script, you need to select the controls or objects in the application-under-test using either the Object Finder Tool method or the Test Object Browser method.
    - Working with datasets
      A dataset is a collection of related data records which supplies data values to the variables in a test script during test script playback.
    - Creating a dataset
      A dataset is a collection of related data records which supplies realistic data values to the variables in a test script during test script playback. You can create data from scratch or import existing data into a new dataset from another dataset or a .csv file.
    - Importing to datasets
      You can import test data into a dataset using a comma-separated value (CSV) file that enables you to import large volumes of test data to a dataset rather than manually entering them.
    - Inserting data-driven commands into a script by using an application visual
      You can add data-driven commands to the script by using an application visual.
    - Associating a dataset with a group in a simplified script
      You can associate a dataset with a group in a simplified script. With this capability, you can create multiple datasets for a script and associate the datasets with the groups in a script.
    - Encrypting datasets
      To secure test data, you must encrypt datasets. You can encrypt one or more columns of a dataset using a password. You are prompted to enter your password when you run a test that utilizes dataset with encrypted variables.
    - Decrypting Datasets
      You must decrypt the dataset if you want to export a dataset into a .csv file. If you decrypt a dataset, it revokes the protection offered to the test data in it.
    - Editing datasets
      After you data-drive a test to create a dataset or create an empty dataset, you can edit the records and variables in the dataset.
    - Replacing literals with dataset references
      If you have an existing test script, you can replace literal values in the script with dataset references to add realistic data to the script. You can find and replace all literals, or just the number, string, or boolean literals with a dataset reference.
    - Dataset references and verification points
      When you create a verification point with a dataset reference, you can supply variable data to make your tests more realistic.
    - Changing the dataset record selection order
      The test dataset record selection order determines how a test script accesses records in the test script's associated dataset when you play back the test script.
    - Associating a dataset with a test script
      You can associate a test script with a dataset to use external data to drive the application instead of using a literal value.
    - Associating a test script with a dataset
      You can associate a test script with a dataset to use external data to drive the application instead of using a literal value.
    - Linking datasets to a functional test script
      You can link datasets to a functional test script to override the existing dataset that is associated with the script. To link a dataset, you must include the functional test script in a compound test in the UI Test perspective, and then map the required dataset by using Dataset Mapper.
    - Removing a dataset association
      You can remove dataset association with a test script.
    - Deleting a dataset
      You can delete a dataset if you no longer require it.
    - Replacing literals with dataset references in the Visual Studio IDE
      If you have an existing test script, you can replace literal values in the script with dataset references to add realistic data to the script. You can find and replace all literals, or selectively replace the number, string, or boolean literals with a dataset reference.
  - Testing terminal-based applications
    Use the HCL DevOps Test UI (Test UI) Terminal-based Applications feature to create test scripts and automate your host-application test cases. You can test host attributes, host field attributes, and screen-flow through a host application. It uses terminal verification points and properties, as well as synchronization code to identify the readiness of terminal for user input.
- Extending the UI Test perspective with custom Java™ code
  You can use custom code to extend the default Web UI testing capabilities. You can write custom Java™ code and call the code from the test. You can also specify that results from the tests that are affected by your custom code to be included in reports.
- Extending the Functional Test perspective
  You can use custom code to extend the default functional testing capabilities. You can write custom code and call the code from the test. You can also specify that results from the tests that are affected by your custom code to be included in reports.
- Extending the functionality in the Visual Studio IDE
  These topics describe various ways that you can customize HCL DevOps Test UI (Test UI) or use the application programming interface (API) to extend Test UI functionality.
- Experimental features
  HCL DevOps Test UI (Test UI) contains a set of pre-releases that enable you to test various experimental features. These experimental features, while still in progress, are introduced early in the release to seek your feedback on its overall functionality and performance. You can play around with these capabilities before they are made available and supported as a general feature in an upcoming release.
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).
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.

Creating a dataset

A dataset is a collection of related data records which supplies realistic data values to the variables in a test script during test script playback. You can create data from scratch or import existing data into a new dataset from another dataset or a .csv file.

Procedure

Click Create a Test dataset (). The Create New Dataset Location and Filename dialog is displayed.
Click the project that must contain the dataset. The selected project is displayed in the Enter, create, or select the parent folder field.
In the Name field, enter the required name of the dataset, and click Next.
Optional: In the Description, enter the required description for the dataset.
In the Dimensions field, specify the number of rows and columns for the dataset.
Click Finish. The new dataset is displayed in a browser.