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.
Modification of Web UI tests
With Test Editor, you can view and customize a Web UI test that is created in Test Hub.
Adding conditional logic and redefining the flow in tests from the Flow catalog
When you want to add conditional logic and redefine the flow to update a test, you can add such steps from the Flow catalog. You can add a test inside the test as a step and abort the test after marking it as failed. Also, you can insert the If, While, and Do-While conditions in the test to make a set of steps run only if a specific condition is met.
Adding a Fail step
You can abort the test and mark the test as failed. For example, you can add the Fail element as a resulting step after checking a condition by using the If statement.

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.
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, and test suites 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 failed steps in test scripts.
  - 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.
    - Editing a Web UI test
      You can edit a Web UI test to add new steps, remove the existing steps, or update the step details.
    - Adding user actions in a test from smartshots
      When you want to add user actions as steps in an existing Web UI test, you can add such steps from smartshots associated with the test. You can select a graphical element in the smartshot and add a user action for that element.
    - New test steps from the General catalog
      When you want to add a log statement, verification point, and variable assignment as a step, you can add those steps from the General catalog. You can also add pausing of the test for a specific duration as a test step.
    - New steps for UI-related actions and user actions in a test from the UI catalog
      When you want to add UI-related actions and user actions to update a test, you can add those steps from the UI catalog. UI-related actions are actions such as opening a new page and adding a new section in the test. User actions are actions such as click, select, type, and key press for user inputs.
    - Adding conditional logic and redefining the flow in tests from the Flow catalog
      When you want to add conditional logic and redefine the flow to update a test, you can add such steps from the Flow catalog. You can add a test inside the test as a step and abort the test after marking it as failed. Also, you can insert the If, While, and Do-While conditions in the test to make a set of steps run only if a specific condition is met.
      - Adding a Run step
        When you want to add a test inside the test as a step, you can use the Run step from the Flow catalog.
      - Adding a Fail step
        You can abort the test and mark the test as failed. For example, you can add the Fail element as a resulting step after checking a condition by using the If statement.
      - Adding an If step
        You can insert the If logic in a test to make a set of steps run only if a specific condition is met.
      - Adding a While step
        You can insert the While logic in a test to make a set of steps run in a loop only if a specific condition is met.
      - Adding a Do-While step
        You can insert the Do-While logic in a test to make a set of steps run in a loop only if a specific condition is met after the first iteration.
    - Disabling test steps
      When you want to exclude a step or a set of steps under a container from the test run, you can disable such steps in a Web UI test.
    - Configuring timeouts for tests and test steps
      You can configure timeouts for tests and individual steps to define the duration of the time that the system should wait before marking an action as failed due to timeout.
    - Copying test steps from one test to another
      When a set of steps in a test is required in another test, you can copy them and paste them into an existing test or an empty test. You can select the required steps from a test to copy, although they are not in a sequence. If there are any variables associated with the selected step, they are also copied with the step.
  - 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.
  - Test creation by Test Genie - Tech Preview
- 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.
- 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).
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.

Adding a Fail step

You can abort the test and mark the test as failed. For example, you can add the Fail element as a resulting step after checking a condition by using the If statement.

Before you begin

You must have completed the following tasks:

Ensured that you are assigned a Team Space Owner, Project Owner, or Member with a Tester role to create or edit a test resource.
Read and understood the information in Edit branch overview and Create or select an Edit branch.
Ensured that your project contains a Web UI test.

Opened the test in Test Editor. See Editing a Web UI test.

Procedure

Click the button displayed on the Test Editor page.

The Edit button appears only when no active edit branch is selected.

Alternatively, right-click the test in the test navigator panel and select Edit.

The Edit branch dialog is displayed.

If the Edit branch dialog is not displayed, then go to step 3.
Select an existing edit branch or create a new edit branch.
Drag and drop the Fail element under any test step as required from the Flow catalog in the Catalog tab.
Click the Fail step.
The step details pane is displayed.
Enter a custom message in the Fail statement text box.
Click the Save icon to save the modifications.

Results

You have added a Fail step from the Flow catalog to mark the test as failed.

What to do next

You can run the test and view the results. See Running a Web UI test.