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.
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.
Test run considerations for schedules
Before you configure a Rate Schedule or VU Schedule run, you must first read the considerations that you need to take into account.

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.
  - Test run considerations for AFT Suites or Functional tests
    Before you configure an AFT Suite or a Functional test run in HCL DevOps Test Hub (Test Hub), you must first read the considerations that you need to take into account.
  - Test run considerations for API Suites or API tests
    Before you configure an API Suite or API test run, you must first read the considerations that you need to take into account.
  - Test run considerations for browser-based Web UI tests
    Before you configure a Web UI test or a Compound Test that contains Web UI tests, which use either the Chrome or Edge browsers, you must first read the considerations that you need to take into account.
  - Test run considerations for JMeter tests
    Before you can run JMeter tests on HCL DevOps Test Hub (Test Hub), you must read the considerations that you must take into account and complete the tasks indicated.
  - Test run considerations for JUnit tests
    Before you can run JUnit tests on HCL DevOps Test Hub (Test Hub), you must read the considerations that you must take into account and complete the tasks indicated.
  - Test run considerations for using Machine learning capabilities
    Before you configure a Performance Test or Schedule run to use Machine learning (ML) capabilities, you must first read the considerations that you need to take into account.
  - Test run considerations for Postman tests
    Before you can run Postman tests on HCL DevOps Test Hub (Test Hub), you must read the considerations that you must take into account and complete the tasks indicated.
  - Test run considerations for schedules
    Before you configure a Rate Schedule or VU Schedule run, you must first read the considerations that you need to take into account.
  - Test run considerations for Selenium tests
    Before you can run Selenium tests on HCL DevOps Test Hub (Test Hub), you must read the considerations that you must take into account and complete the tasks indicated.
  - Test run considerations for using mobile device clouds
    Before you configure runs of tests that use mobile device clouds as the location, you must first read the considerations that you need to take into account.
- 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.
- 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 system
  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 system 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.

Test run considerations for schedules

Before you configure a Rate Schedule or VU Schedule run, you must first read the considerations that you need to take into account.

Important information about JMeter tests in schedules

When you want to run JMeter tests as part of the VU Schedule or Rate Schedule on HCL DevOps Test Hub (Test Hub), you must have completed the following tasks:

Installed the HCL DevOps Test Performance Agent on a computer.
Installed the JMeter application on the computer where you have installed the HCL DevOps Test Performance Agent.
Set the environment variable JMETER_HOME that points to the JMeter installation directory.

Important information about Resource Monitoring sources in schedules

When you want to run schedules on Test Hub, you must have completed the following tasks in Test Performance:

Created a performance schedule of Rate or VU type.
Added Resource Monitoring sources, or the labels of Resource Monitoring sources to a schedule. Refer to Adding resource monitoring sources to a performance schedule by using labels.

Before you configure a run of a Schedule, you must complete the following tasks in Test Hub:

Add Resource Monitoring sources to your project in Test Hub. See Monitoring an NGINX server.
Enable Test Hub as Resource Monitoring service only if you want to replace Resource Monitoring labels set in Test Performance with the labels that you created in Test Hub. See Controlling resource monitoring sources in a schedule.
Perform the following steps when you want to override the Resource Monitoring labels in the test asset with the Resource Monitoring labels that you create in Test Hub:
1. Click the Resource Monitoring tab.
  
  Note:
  The Resource Monitoring tab displays only if you enabled the Resource Monitoring from Service option in Test Performance when you created the test asset.
2. Click , and press the Ctrl + Space bar keys, or enter the initial letter of a label to select a label in the list.
  
  Note:
  You can select or add labels only if you added the labels in the Resource Monitoring Sources page in Test Hub.

For running a Rate Schedule or VU Schedule, see Configuring a run of a Rate Schedule or VU Schedule.