Home
Test Manager Guide
This guide describes how to manage and track your overall test effort. This guide is intended for test managers.
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.
Secrets configuration
If you are working with an API suite and the project test asset contains environment variables that are required for the test runs, you must configure the environment variables as secrets in a classification by using the Add Secret option in the Security page. Configuring secrets enable the API suite to run correctly on Test Hub.

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.
  - Working with projects in a team space
    After you log in to HCL DevOps Test Hub (Test Hub), you must have a project to perform the test activities. To work with projects, you must create and configure projects.
  - Repository considerations for a server project
    To collaborate with other project stakeholders, you can open test assets from a local clone of a remote repository, pull project test assets from the remote repository, and push changes made to your local test assets to the remote repository. Before you add a project and then add a repository to that project, you must consider some information about repositories.
  - Adding a project
    The first step is to add a project and provide some details about it.
  - Adding repositories to a server project
    You can add a single repository individually or multiple repositories simultaneously to a server project to access assets and resources that are available in the repositories.
  - Secrets configuration
    If you are working with an API suite and the project test asset contains environment variables that are required for the test runs, you must configure the environment variables as secrets in a classification by using the Add Secret option in the Security page. Configuring secrets enable the API suite to run correctly on Test Hub.
  - Adding users to a project
    You can add users to your project in HCL DevOps Test Hub (Test Hub) so that they can access your test assets.
  - Viewing active projects
    After you log in to HCL DevOps Test Hub (Test Hub), you can view both active and archived projects in the Initial team space.
  - Changing the visibility configuration of a project
    After you create a project in HCL DevOps Test Hub (Test Hub), you might want to change the visibility configuration of the project from the public, which is the default, to private.
  - Becoming a project member
    You might want to request to be a member of another project. New users without any projects might also want to be a member of an existing project.
  - Managing access to the server projects
    You might want to add or remove a project member role from your project.
  - Archiving or unarchiving server projects
    You can archive a project when that project is no longer needed but you want to retain it for future reference. If you do want to use an archived project, you can unarchive it.
  - Deleting server projects
    You might want to delete a project when the project is no longer needed, and you want to free up disk space.
  - Project overview
    After you configure a project with one or more Git repositories and run some test assets, you can view statistics about those test assets.
- 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 API 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 classification. You can create classification 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).
- Managing notifications
  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 an SMTP server on Test Hub when you want Test Hub to send out notifications about the 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.

Secrets configuration

If you are working with an API suite and the project test asset contains environment variables that are required for the test runs, you must configure the environment variables as secrets in a classification by using the Add Secret option in the Security page. Configuring secrets enable the API suite to run correctly on Test Hub.