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.
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.
Suite creation with Test Genie
Test Genie is an AI-powered capability that can create a scenario-based suite from requirements and design context, and then create tests for all generated intents in a single run.

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.
- 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.
  - Creating a suite
    You can create a suite within your project in HCL DevOps Test Hub (Test Hub). You can add multiple tests and suites into a single suite for a test run.
  - Suite creation with Test Genie
    Test Genie is an AI-powered capability that can create a scenario-based suite from requirements and design context, and then create tests for all generated intents in a single run.
    - Creating a suite with AI-generated scenarios and tests
      You can create a scenario-based suite and then generate tests for all scripts in a single run by using AI-powered Test Genie. This bulk generation helps to streamline test creation for multiple scripts in a single run.
  - Modifying a suite
    You can modify the existing suite within your project in HCL DevOps Test Hub (Test Hub) by adding, removing, or rearranging the tests and suites in a suite.
  - Running a suite sequentially
    When you want tests to run one after the other, you can run a suite sequentially that maintains the correct order and accuracy of the test results.
  - Running a suite concurrently
    You can run a suite to run multiple tests and other suites in parallel to expedite the testing process.
  - Running multiple suites or tests by using the wildcard pattern
    When you want to enable a single suite to run multiple tests and suites based on their name, you can use a Run step to refer to tests and suites by using wildcard patterns. You can also use these patterns to specify the suites that must be excluded.
  - Running suites on multiple browsers and devices
    You can now configure a test suite to run across multiple web browsers and supported devices in one consolidated run. Instead of managing separate test runs for each browser and device, you can define all of your target browsers and devices within the configuration of the test suite. This simplifies cross-browser validation, saves time, and provides comprehensive report.
  - Accessing the console output
    When you run suites, you can access the console output that provides information such as error messages, logs, and the test verdict. You can then use this output to troubleshoot issues by reviewing details, such as session IDs and error messages.
  - Stopping test runs within a suite
    You can stop the tests that run within a suite when issues occur or if you decide to stop the run before completion.
  - Rerunning failed tests in a suite
    When you run tests in a suite, a few tests might fail. You can rerun the failed tests instead of rerunning the suite.
  - Deleting a suite
    You can delete a suite when it is no longer required in your project.
- 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.

Suite creation with Test Genie

Test Genie is an AI-powered capability that can create a scenario-based suite from requirements and design context, and then create tests for all generated intents in a single run.

Suite generation with Test Genie helps you start test authoring from a high-level feature intent instead of manually creating each test. You can provide suite context such as a summary, optional scenario, and optional UI reference images. Test Genie then creates empty tests that contain Open steps and AI-generated intents for each scenario.

After you review or edit the generated intents, you can generate tests for the entire suite from the suite toolbar. Test generation runs in one flow for all tests in the suite. As each test is generated, Test Genie uploads the tests incrementally to the suite.

To use Test Genie, you must configure at least one AI provider in the Infrastructure > Cloud Credentials page of Test Hub. Test Genie supports the following AI providers:

Anthropic - Tech Preview
OpenAI
GitHub Copilot
Restriction:
Only one test generation session through GitHub Copilot can be active at a time across the entire Test Hub server. Any additional Copilot requests are queued and wait until the current session completes.

For optimal results, you can use OpenAI with the GPT-5.4-mini model.

Session limits for AI generation

In Test Hub, you can configure session limits as Advanced configuration values when you add a cloud credential for an AI provider in Cloud Credentials. These values are saved with the selected provider credential and are applied whenever Test Genie starts a suite or test generation session by using that credential.

The three limits are Max tokens per session, Max interactions per session, and Max duration per session (in seconds). During test generation, Test Hub evaluates all three limits. If any configured limit is reached, the active AI conversation session ends, and you must start a new session to continue the test generation.

These session limits are optional for OpenAI and Anthropic credentials and are not applicable for GitHub Copilot credentials. By configuring these values, you can control response depth and generation time with platform resource usage for large or complex suite-generation workloads.