Home
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.
Configuration of test runs in a GitHub Actions Workflow
You can configure test runs of test resources that are in a project repository of HCL DevOps Test Hub (Test Hub) in a GitHub Actions Workflow. You can choose to run test resources that are in your server project in the GitHub Workflow when you do not want to run the test resources without opening the Test Hub project.
Prerequisites to run tests in a GitHub Actions Workflow
Before you configure a test run for any test resources that are in a project repository of HCL DevOps Test Hub (Test Hub), you must complete certain tasks to run the test resources in a GitHub Actions Workflow.

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.
- System modeling
  You can use the system model feature on HCL DevOps Test Hub (Test Hub) to create a model that simulates an application or system under test. You can define components to represent the actual components in the system under test, define their relationships and then view the components in a system under test as a diagrammatic representation.
- Prerequisites to running tests
  Before you can run a test asset in a project on HCL DevOps Test Hub (Test Hub), you must read the information about the different tests assets. You can add a remote static agent, Docker host, or Kubernetes cluster to the project and then select it as an alternate location to run the test assets.
- Management of agents
  You can find information about managing performance agents or API agents that you install on remote computers and then configure the remote agents to register with HCL DevOps Test Hub (Test Hub). After the agents are registered, you can add them to your projects and then select them as locations to run tests or virtual services.
- Management of Docker hosts
  You can find information about the tasks that you can perform on remote Docker hosts. After you set up a remote Docker host, you can register the Docker host with HCL DevOps Test Hub (Test Hub). You must then add the registered remote Docker host to your project before you can run tests on the remote Docker host location.
- Management of remote Kubernetes clusters
  You can find information about the tasks that you can perform on remote Kubernetes clusters. After you set up a remote Kubernetes cluster, you can register the external cluster with a team space on HCL DevOps Test Hub (Test Hub). You must then add the remote cluster to a project before you run test assets or resources on the remote Kubernetes cluster.
- Management of mobile device cloud credentials
  You can find information about managing the credentials that are required to connect to mobile device clouds from HCL DevOps Test Hub (Test Hub).
- Test run configurations
  You can configure and run tests in HCL DevOps Test Hub (Test Hub) after you add the test resources to your project in your team space.
- Configuration of test runs in a GitHub Actions Workflow
  You can configure test runs of test resources that are in a project repository of HCL DevOps Test Hub (Test Hub) in a GitHub Actions Workflow. You can choose to run test resources that are in your server project in the GitHub Workflow when you do not want to run the test resources without opening the Test Hub project.
  - Prerequisites to run tests in a GitHub Actions Workflow
    Before you configure a test run for any test resources that are in a project repository of HCL DevOps Test Hub (Test Hub), you must complete certain tasks to run the test resources in a GitHub Actions Workflow.
  - Configuring a test run in a GitHub Actions Workflow
    After you complete the prerequisite tasks to run tests in a GitHub Actions Workflow, you can configure the test run in a GitHub Actions Workflow. The test is in a project on HCL DevOps Test Hub (Test Hub).
- Configuration of a scan of an application code
  You can use HCL DevOps Test Hub (Test Hub) to scan your application code for security vulnerabilities similar to using the HCL® AppScan CodeSweep plugin to scan code in Visual Studio.
- Management of running tests
  Find information about the tasks that you can perform on a test that you configured for a run either while it runs or after it completes the run.
- Management of virtualized services
  You can find information about the tasks that you can perform on and manage the virtualized services that run on HCL DevOps Test Hub (Test Hub). You can start or stop the virtual services that are available to Test Hub. You can view the routing rules and usage statistics of virtualized services, agents, or intercepts that are connected to Test Hub.
- Test results
  After the tests, Suites, or schedules are run and completed, you can view the results and open the reports in HCL DevOps Test Hub (Test Hub) to analyze the verdict, the performance, and statistics. You can also re-execute tests and schedules from the Results page with the same commit id.
- Machine learning capabilities in DevOps Test Hub
  HCL DevOps Test Hub (Test Hub) uses Machine learning (ML) algorithms to analyze tests that match certain requirements and criteria, and then presents the findings as insights and recommendations after the tests are run. You can use the insights and recommendations to interpret the test results and identify the problem areas in the system under test.
- Resource monitoring
  When you apply load to a system under test, the amount of resources consumed by your system is increasing. If the capacity of the resources does not match the load, you can see performance issues in the results. Resource monitoring in HCL DevOps Test Hub (Test Hub) helps you monitoring the resources of a system and establish the performance metrics and usage data of the system. Thus, you can observe the health of these resources while a schedule is running.
- Configuration of a change management
  When you use any application to create and track defects (bugs), issues, or other work items, you can configure the application as a change management on HCL DevOps Test Hub (Test Hub). You can then create defects (bugs), issues, or other work items without the need to open your application.
- Integrations with other applications
  You can integrate certain applications with HCL DevOps Test Hub (Test Hub) to run tests, view the test results, and create defects.
- Managing access to DevOps Test Hub
  Desktop clients and third-party integrations use offline user tokens to connect to HCL DevOps Test Hub (Test Hub).
- Working with DevOps Test Hub REST services
  When you want to use the REST APIs of HCL DevOps Test Hub (Test Hub) in your test automation scripts, you can view the REST APIs that are exposed by Test Hub. You can also run the APIs from within your project in Test Hub.

Prerequisites to run tests in a GitHub Actions Workflow

Before you configure a test run for any test resources that are in a project repository of HCL DevOps Test Hub (Test Hub), you must complete certain tasks to run the test resources in a GitHub Actions Workflow.

You must be familiar with creating projects and running test resources from Test Hub.

You must complete the following tasks to set up and use Test Hub:

Install Test Hub. See Installation of DevOps Test Hub.
Possess valid licenses to use Test Hub. See Management of licenses in DevOps Test Hub.
Create a project on Test Hub. See Adding a project.
Add a repository that contains test resources to the project repository. See Adding repositories to a server project.
Generate the Offline User Token on Test Hub that is required for connecting to Test Hub from another application such as the GitHub Action. See Managing access to DevOps Test Hub.
Open the project to view the details of the test resources that you want to run in a GitHub Actions Workflow. You must make a note of the test resource details from the Execution page of Test Hub.
You must note the following details of the test resource that are to be provided in the YAML file for the GitHub Action:
- The URL of the Test Hub instance.
- The name of the team space that contains the project on Test Hub.
- The name of the project on Test Hub that contains the test resources.
- The branch name of the project repository that contains the test resources.
- The ID of the test resource.

You must complete the following tasks outside of Test Hub:

Create an empty Git repository on any GitHub Enterprise server, if you do not already use Git repositories to store the test resources that you create. For more information about creating Git repositories, refer to Creating a new repository.
If you already use Git repositories to store test resources created, you can use the same Git repositories.
Note: You must have the required privileges in the Git repository to create a GitHub Actions Workflow.
Enable the GitHub Actions option in the Git repository, if it is not available as an option to use. For more information about enabling the GitHub Actions, refer to Learn about GitHub Actions.

You can continue to configure a run of a test, see Configuring a test run in a GitHub Actions Workflow.