Home
Test Execution Specialist Guide
This guide describes tasks that you must complete before you can configure and run tests in HCL OneTest™ Server. 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 OneTest™ Server, 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 JUnit tests
Before you can run JUnit tests on HCL OneTest™ Server, you must read the considerations that you must take into account and complete the tasks indicated.

Test Execution Specialist Guide
This guide describes tasks that you must complete before you can configure and run tests in HCL OneTest™ Server. 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 OneTest™ Server 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 OneTest™ Server, 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, 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 schedules
    Before you configure a Rate Schedule or VU Schedule run, you must first read the considerations that you need to take into account.
  - Considerations for using Jaeger traces in reports
    Before you can use Jaeger to report the test results in the supported tests, you must read the considerations that you must take into account.
  - Test run considerations for JMeter tests
    Before you can run JMeter tests on HCL OneTest™ Server, 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 OneTest™ Server, you must read the considerations that you must take into account and complete the tasks indicated.
  - Test run considerations for Postman tests
    Before you can run Postman tests on HCL OneTest™ Server, you must read the considerations that you must take into account and complete the tasks indicated.
  - Test run considerations for Selenium tests
    Before you can run Selenium tests on HCL OneTest™ Server, you must read the considerations that you must take into account and complete the tasks indicated.
- 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 OneTest™ Server. 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 OneTest™ Server. 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 OneTest™ Server. You must then add the remote cluster to a project before you run test assets or resources on the remote Kubernetes cluster.
- Test run configurations
  You can configure and run tests in HCL OneTest™ Server 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 OneTest™ Server 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 HCL OneTest Server project.
- Configuration of a scan of an application code
  You can use HCL OneTest™ Server 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 OneTest™ Server. You can start or stop the virtual services that are available to HCL OneTest Server. You can view the routing rules and usage statistics of virtualized services, agents, or intercepts that are connected to HCL OneTest Server.
- Test results
  After the tests, Suites, or schedules are run and completed, you can view the results and open the reports in HCL OneTest™ Server to analyze the verdict, the performance, and statistics. You can also re-execute tests and schedules from the Result page with the same commit id.
- 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 OneTest™ Server 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 OneTest™ Server. 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 OneTest™ Server to run tests, view the test results, and create defects.
- Managing access to HCL OneTest™ Server
  Desktop clients and third-party integrations use offline user tokens to connect to HCL OneTest™ Server.
- Working with HCL OneTest™ Server REST services
  When you want to use the HCL OneTest™ Server REST APIs in your test automation scripts, you can view the REST APIs that are exposed by HCL OneTest Server. You can also run the APIs from within your project in HCL OneTest Server.

Test run considerations for JUnit tests

Before you can run JUnit tests on HCL OneTest™ Server, you must read the considerations that you must take into account and complete the tasks indicated.

Before you run JUnit tests, you must have completed the following tasks:

You must ensure that the JUnit extension on HCL OneTest™ Server is enabled. You must enable the JUnit extension at the time of installation of the server software or before you add the repository that contains the JUnit tests to the server project. See Enabling server extensions.
You must have created the JUnit tests that use JDK 8, as part of a Maven V3.6.3 project. The Maven project must contain the Maven Surefire plug-in, which is required to run the JUnit tests contained in the Maven project. The Maven project as a pom.xml must be committed to the remote repository.
Note: If you create the JUnit tests on other versions of JDK, you must copy the JDK version to the userlibs pod under the /data/junit-ext/jdks directory. See Copying third-party application Jars to Kubernetes.

Restriction: You cannot run the test assets on a remote Docker host.