Welcome
Test Author Guide
This guide describes how to create and edit test assets in HCL DevOps Test Hub (Test Hub), and then publish test assets to the remote Git repository that you have configured in your project. This guide is intended for testers and test managers.
Web UI test management
You can test your web applications by recording Web UI tests in HCL DevOps Test Hub (Test Hub). Test Hub supports industry-standard browsers such as Google Chrome, Microsoft Edge, and Mozilla Firefox to record and play back Web UI tests. After the playback, you can evaluate the test results.
Salesforce Lightning tests
You can record and play back Web UI tests for Salesforce applications that use Salesforce Lightning controls.
Configuration of Salesforce test automation
You must configure HCL DevOps Test Hub (Test Hub) and Salesforce application before you record and play back Salesforce Lightning application tests.
Configuration of the Salesforce application for OTP-based authentication
You can configure Salesforce and HCL DevOps Test Hub (Test Hub) for OTP-based authentication during Salesforce test automation.
Creating the OTP secret in Test Hub
You can create the otpauth:// secret URI in Test Hub to map it to the Verification_Code variable, so that the OTP value resolves automatically at run time.

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 Hub (Test Hub). 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 Hub (Test Hub).
Getting Started Guide
This guide provides an introduction to HCL DevOps Test Hub (Test Hub) covering key features, task flows, and setup instructions. You can get started with installation, integration, user access management, and core functionalities like test data creation, test asset management, and reporting. This guide is intended for new users.
Tutorials
Learn how to perform frequently used tasks, including creating and managing Web UI tests and viewing test results through functional reports.
Administrator Guide
This guide describes how to install the HCL DevOps Test Hub (Test Hub) software.
Test Author Guide
This guide describes how to create and edit test assets in HCL DevOps Test Hub (Test Hub), and then publish test assets to the remote Git repository that you have configured in your project. This guide is intended for testers and test managers.
- Edit branch overview
  When you want to create or modify a test resource in HCL DevOps Test Hub (Test Hub), you must use an Edit branch. An Edit branch is a temporary branch created from the selected branch in the repository configured within the project, where you can save the created or edited resource.
- Test Editor overview
  You can use the Test Editor tab to create and manage test assets such as applications, Web UI tests, test suites, and environments in HCL DevOps Test Hub (Test Hub).
- Application management
  When you want to create and manage Web UI tests in HCL DevOps Test Hub (Test Hub), you must first create an application within the project.
- Web UI test management
  You can test your web applications by recording Web UI tests in HCL DevOps Test Hub (Test Hub). Test Hub supports industry-standard browsers such as Google Chrome, Microsoft Edge, and Mozilla Firefox to record and play back Web UI tests. After the playback, you can evaluate the test results.
  - Web UI test creation
    You can create Web UI tests by using the recording option or the empty test option in the HCL DevOps Test Hub (Test Hub). Test Hub automatically enables web browsers and provides DevOps Test Runtime or the recording agent to configure the test environment before you start recording tests for web applications.
  - Running a Web UI test
    You can run a Web UI test in HCL DevOps Test Hub (Test Hub) after you record the test, and to verify that the web application performs as expected.
  - Viewing step-level results and updating tests
    You can view the step-level results of each step after running a Web UI test. You can edit and update the steps in test scripts by replacing smartshots.
  - Stopping a test run
    You can stop a test run when issues occur or if you decide to stop the run before completion.
  - Modification of Web UI tests
    With Test Editor, you can view and customize a Web UI test that is created in Test Hub.
  - Renaming a test asset
    You can rename test assets such as tests, suites, smartshots, and applications in your project by using the Rename option.
  - Deleting a test asset
    You can delete an application, test, suite, or smartshot when it is no longer required in your project. If the test asset that is selected for deletion is referenced in another test or a test suite, or if the selected smartshot is referenced in a test, a warning is displayed.
  - Creating a test module from an existing set of steps
    When a set of steps are repeated and required in multiple tests, you can create a test module for such repeatable steps. You can select the required steps that are in sequence from an existing test and extract them to create a new test module. After extraction, the selected steps are replaced by the Run step and the new test module is listed in the test navigator panel.
  - Viewing test assets exported from DevOps Test UI
    When you export Web UI test projects from HCL DevOps Test UI (Test UI) to HCL DevOps Test Hub (Test Hub), Test UI extracts test assets, processes them, and generates a .yaml file that contains the step details and the associated smartshots. You can then view the test assets of the Web UI test projects that are exported from Test UI.
  - Salesforce Lightning tests
    You can record and play back Web UI tests for Salesforce applications that use Salesforce Lightning controls.
    - Configuration of Salesforce test automation
      You must configure HCL DevOps Test Hub (Test Hub) and Salesforce application before you record and play back Salesforce Lightning application tests.
      - Configuration of Test Hub for Salesforce test automation
        You can configure HCL DevOps Test Hub (Test Hub) variables, environments, datasets, and runtime parameters for Salesforce test automation.
      - Configuration of the Salesforce application for OTP-based authentication
        You can configure Salesforce and HCL DevOps Test Hub (Test Hub) for OTP-based authentication during Salesforce test automation.
        Registering an authenticator app for OTP-based sign-in
        You must register a time-based one-time passcode (TOTP) authenticator for the Salesforce automation user, so that Test Hub can generate matching one-time passcodes during sign-in.
        Creating the OTP secret in Test Hub
        You can create the otpauth:// secret URI in Test Hub to map it to the Verification_Code variable, so that the OTP value resolves automatically at run time.
    - Recording and configuring Salesforce application tests
      You can record Salesforce Lightning application interactions from the Test Editor and configure the recorded test with credential and OTP values for different users.
    - Running a Salesforce Lightning application test
      You can run the recorded Salesforce Lightning application tests and add steps or verification points from Smartshots.
- Test suite management
  A suite is a collection of the tests and other suites. You can combine the multiple tests and suites into a single workflow and organize them into a suite.
- Test variables
  A test variable is a user-defined, name-value pair that stores and refers to information throughout a test. You can assign the value of a variable to a test element or assign the value of a UI object property to a test variable.
- Test environments
  You can define custom environments to manage sets of variables such as application URLs and user credentials, and to configure profile overrides. When you run a test, the variables and override rules defined in the environment dynamically replace the values within your test script. You can easily change testing targets without modifying your test script by using environments because the environment-level configurations take precedence over the default values defined in the script.
- Catalog management
  You can use the data catalog in HCL DevOps Test Hub (Test Hub) to browse and manage data generators used in test data creation. The catalog section provides access to built-in generators, allows you to create custom generators tailored to specific needs, and group them using custom categories.
- Data management
  Effective data management is at the core of robust application testing. In HCL DevOps Test Hub (Test Hub), you can manage test data by using the Data tab, which provides a centralized workspace for handling various types of data. Whether you work with fabricated data, retrieve information from databases, or define structured schemas, this interface supports both creating new data and reusing existing assets across your testing requirements.
- Publishing all changes in an Edit branch
  After you create or modify any data or test assets in an Edit branch of a project in HCL DevOps Test Hub (Test Hub), you can publish all the changes that are in an Edit branch to the source branch in the project repository. After publishing, other members in the project can view and use the resources.
Test Execution Specialist Guide
This guide describes tasks that you must complete before you can configure and run tests in HCL DevOps Test Hub (Test Hub). You can find information about configuring runs for the different test types that are supported. You can also find information about other tasks that you can perform on the Resource Monitoring Service, Virtualization, and Integrations with third-party applications. This guide is intended for testers or test execution specialists.
Test Manager Guide
This guide describes how to manage and track your overall test effort. This guide is intended for test managers.
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 Hub (Test Hub).
Unable to publish test assets to a Control repository
When you attempt to publish test assets from HCL DevOps Test Hub (Test Hub) to a Control repository, the publish operation might fail with the following message: Remote rejected; pre-receive hook declined.
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 Hub (Test Hub) as a PDF file.
Security Considerations
This document describes the actions that you can take to ensure that your installation is secure, customize your security settings, and set up user access controls in HCL DevOps Test Hub (Test Hub).
Notices
This document provides information about copyright, trademarks, terms and conditions for the product documentation.

Creating the OTP secret in Test Hub

You can create the otpauth:// secret URI in Test Hub to map it to the Verification_Code variable, so that the OTP value resolves automatically at run time.

Before you begin

You must have completed the following tasks:

Obtained the otpauth:// secret URI. See Registering an authenticator app for OTP-based sign-in.
Ensured that a security group is configured for the project. See Configuring the initial test environment.

About this task

You store the otpauth:// secret URI as a secret in the project's security group, and then reference that secret from the Verification_Code variable in your environment file. Test Hub uses the secret to generate the matching OTP value at run time.

Procedure

Log in to Test Hub.
The Projects page of the initial team space is displayed.
Click My projects > project_name to open the project that contains the Salesforce application.
The Overview page of the project is displayed.
Click Manage > Security.
Click + Add Secret.
Enter an identifier for the secret in the Identifier field. For example, salesforceOtpSecret.
Paste the copied otpauth:// secret URI in the Value field.
Click Create to save the secret.
Open the environment file. For example, SFEnv.dte.yaml in the Test Editor page.
Add a Verification_Code entry with the following values:
- Set expr to the identifier of the secret that you created. For example, salesforceOtpSecret.
- Set type to secret.
You can configure different OTP secrets for different users in the same environment file.

Results

You have created the OTP secret in the project's security group.