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.
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.
Viewing the system model
You can view an existing system model that is in a team space in HCL DevOps Test Hub (Test Hub) if you are a member of the team space.

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.
  - Task flows for working with a system model
    You can find information about the tasks that you can perform when you want to create a system model, components, associate the components, create linkages among the components, and then publish the system model to the team space repository. You can also find information about the tasks that you must perform when you want to modify an existing system model.
  - Adding a repository to a team space
    You must add a repository to the team space in HCL DevOps Test Hub (Test Hub) when you want to create, modify, or store a system model.
  - Creating a system model
    Before you can create components in a system model in HCL DevOps Test Hub (Test Hub), you must create an empty system model and publish the system model to the team space repository.
  - Creating components
    After you create an empty system model in the team space in HCL DevOps Test Hub (Test Hub), you can create components that represent components of the system under test.
  - Creating child components
    You can create child components in the system model in HCL DevOps Test Hub (Test Hub) when you want to represent the sub-components of a component in a system under test.
  - Creating linkages between components
    You can create linkages between components in HCL DevOps Test Hub (Test Hub) to display the relationship between them. The linkages can be between components or between child components of the same or different parent components.
  - Deleting linkages between components
    When you do not want to retain the linkages between components that you created in the system model in HCL DevOps Test Hub (Test Hub), you can delete the linkages.
  - Modifying components
    At any point in time, after you create a component in HCL DevOps Test Hub (Test Hub), you can modify and update the details of the components such as the component type, and the relationships with other components.
  - Deleting components
    When you do not require a component in HCL DevOps Test Hub (Test Hub), you can delete the component from the system model.
  - Publishing changes to the system model
    When you create, delete, or modify components in a system model in HCL DevOps Test Hub (Test Hub), the changes are saved locally and are not visible to the other project members or team space members. You must publish the system model changes to the team space repository to make your changes visible to all users of the team space.
  - Associating resources with components
    After creating components in the system model in HCL DevOps Test Hub (Test Hub), you can navigate to a project in the team space to associate the Suites, tests, or virtual service resources in the project repositories with components in the system model.
  - Viewing resources that are associated with components
    After you associate Suites, tests, or virtual services resources with components in the system model in HCL DevOps Test Hub (Test Hub), you can view the associated resources from the System Model page. You can opt to run an instance of the associated resource or stop a running instance of the associated resource.
  - Removing resources that are associated with components
    When you do not want to retain the resource that you associated with a component in HCL DevOps Test Hub (Test Hub), you can delete the resource association from the system model.
  - Publishing changes of associating or dissociating resources with components
    After you associate or dissociate resources in a project with a component in the system model in HCL DevOps Test Hub (Test Hub), you must publish the changes made to the branch in the project repository so that the association changes are visible to the other members of the project.
  - Viewing the system model
    You can view an existing system model that is in a team space in HCL DevOps Test Hub (Test Hub) if you are a member of the team space.
  - Deleting a system model
    When you want to remove an existing system model to create a new system model in HCL DevOps Test Hub (Test Hub), you must delete the existing system model because only one system model is supported in a team space.
  - Deleting a repository that is added to a team space
    You can delete a repository that you added to the team space in HCL DevOps Test Hub (Test Hub) when you do not want to use a team space repository.
- 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.
- 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 HCL DevOps Test Hub (Test Hub) REST APIs 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.

Viewing the system model

You can view an existing system model that is in a team space in HCL DevOps Test Hub (Test Hub) if you are a member of the team space.

Before you begin

You must be a licensed user of Test Hub and a member of a team space.

Procedure

Log in to Test Hub, if you are not already logged in.
Open the team space to which a team space repository is added.

The Active projects page is displayed.
Click System Model on the left navigation pane.

The System Model page is displayed.

Results

You viewed an existing system model in the team space from the System Model page.