Welcome
Test Manager Guide
This guide describes how to manage and track your overall test effort. This guide is intended for test managers.
Protecting test assets by using secrets
Secrets are key-value pairs that are created for your project in HCL DevOps Test Hub (Test Hub) under a security group. You can create security group for your project that enable you or members in your project to use secrets at test runtime either in Test Hub or in HCL DevOps Test Integrations and APIs (Test Integrations and APIs).
Creating a secret in a security group
You must create secrets in the security groups that is set in your project so that the members of the project with access to the secrets can use them in specific during an API Suite 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.
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.
- Managing team spaces
  You might want to become a team space member, add members to your team space, change a user role in a team space, modify the team space, or delete a team space.
- Managing DevOps Test Hub projects
  HCL DevOps Test Hub (Test Hub) projects manage access to your test assets, which are stored in a Git repository. Projects are maintained in a team space. Projects are either public by default or private. Private projects are not discoverable by other users. You can either add your own project or you can request to be a member of another public project.
- Managing repositories
  After you create a project in HCL DevOps Test Hub (Test Hub), you can add repositories that contain test assets and resources to the project. You can also change the repository details, update the user credentials of a repository, delete a repository, create a webhook for the configured repository.
- Protecting test assets by using secrets
  Secrets are key-value pairs that are created for your project in HCL DevOps Test Hub (Test Hub) under a security group. You can create security group for your project that enable you or members in your project to use secrets at test runtime either in Test Hub or in HCL DevOps Test Integrations and APIs (Test Integrations and APIs).
  - Creating a secret in a security group
    You must create secrets in the security groups that is set in your project so that the members of the project with access to the secrets can use them in specific during an API Suite run.
  - Granting access to members or member roles
    You can grant Read access to the secrets added to the security group in your project at the role level for members of a designated role. Additionally, you can provide Read and Write access to specific members. Without access to the security group, members cannot view, create, edit, delete, or use the secrets added to the security group.
  - Managing secrets
    You can view, edit, or delete the secrets configured under a security group any time after you created secrets or after you were granted access to the secrets security group. You can change the value of the secret by editing the secret. You can delete secrets that you no longer require in your test environment.
- Notification Management
  HCL DevOps Test Hub (Test Hub) provides a feature to display notifications for different events within the user interface (UI) of Test Hub. You can configure Email notifications on Test Hub to send out notifications about different events as emails to the subscribed users. You can also configure third-party applications as webhooks on Test Hub when you want Test Hub to send push notifications about the server events to the third-party applications in a preset template.
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 a secret in a security group

You must create secrets in the security groups that is set in your project so that the members of the project with access to the secrets can use them in specific during an API Suite run.

Before you begin

You must have completed the following tasks:

Created a project on Test Hub.
Created a security group. See Creating a security group.
You must be a member with access to the secrets in the security group. See Granting access to members or member roles.

About this task

You can also configure secrets such that the secrets can be used across different test environments by members with access to the security group. Secrets correspond to the following:

Environment variables or tags that you create in a Test Integrations and APIs project specific to an environment.
Variables that you promote in a server test as a secret that is specific to an environment.

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 test assets.

The Overview page of the project is displayed.
Click Manage > Security.
The Security page is displayed.
Click a security group for which you want to add the secrets under the Security Group.
Click Add Secret.
The Add Secret dialog is displayed.
Enter a name for the secret as its Identifier, and then enter the password as the Value for the secret.

For example, enter the name of the secret to access a database as dbcred and enter the password required to access the database as its value.
Click Create.

A message is displayed that confirms the creation of the secret.

Results

You have created secrets in the selected security group for your project.

What to do next

You can view, edit, or delete the secrets added to a security group any time you want.
You can use the secrets in the tests that require these secrets during test runs.