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.
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 connected 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.
Prerequisites for running virtual services
You can find information about the prerequisite tasks that you must complete before you configure a run of the virtual services on HCL OneTest™ Server.
Prerequisites for running HTTP virtual services
You can find information about the tasks that you must complete before you configure a run of the HTTP virtual services on HCL OneTest™ Server.

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
  In this topic, you can find information about using the system model feature. You can also find the tasks that you can perform to create a system model. You must configure a repository to save the system model that you created for the application under test.
- Prerequisites to running tests
  Before you can configure and run a test in a project on HCL OneTest™ Server, you must read the information about the different tests. You might want to add a remote static agent or a remote Docker host to the project as an alternate location to run the tests.
- Agents overview
  You can find information about the agents that you must install on remote computers and configure the agents with the offline user token so that the agents 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.
- Managing 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 add the registered remote Docker host to your project before you can run tests on the remote Docker host location.
- Test run configurations
  You can configure and run tests in HCL OneTest™ Server after you add the test resources to your project.
- 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 connected 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.
  - Prerequisites for running virtual services
    You can find information about the prerequisite tasks that you must complete before you configure a run of the virtual services on HCL OneTest™ Server.
    - Prerequisites for running HTTP virtual services
      You can find information about the tasks that you must complete before you configure a run of the HTTP virtual services on HCL OneTest™ Server.
    - Prerequisites for running virtualized Istio based services in HCL OneTest™ Server
      You can find information about the tasks that you must complete before you run virtualized Istio based services in HCL OneTest™ Server.
    - Setting up the HTTP proxy
      When you want to run HTTP virtual services on HCL OneTest™ Server, you can set up an HTTP proxy to route requests to the virtual service. You must configure the HTTP proxy with the HCL OneTest Server URL and offline user token generated from HCL OneTest Server so that the HTTP proxy can register with HCL OneTest Server.
  - Viewing intercepts that are registered with HCL OneTest™ Server
    After you install the HTTP proxies and configure them with your offline user token, the proxies register with HCL OneTest™ Server as intercepts and you can view the registered intercepts on the Agents and Intercepts page.
  - Viewing virtual service resources
    When project repositories contain virtual service resources and you want to view the resources so that you can run them, you can view the virtual services from the Resources page in HCL OneTest™ Server.
  - Configuring a run of a virtual service
    When you have virtual service resources that are in the repositories added to your project, you must configure a run of the virtual service to start an instance of the virtual service on HCL OneTest™ Server.
  - Running HTTP virtual services without using proxies
    When you run HTTP virtual services on HCL OneTest™ Server, the endpoint on which the virtual service is exposed externally uses a host name that includes a generated ID. If a client application is required to call the virtual service directly via its external host name and not via the HTTP proxy, then you might want to determine the host name to configure the client first before you start the virtual service.
  - Viewing running instances of virtual services
    After you start virtual services from the Resources page, you can view the instances of the virtual services that are running from the Instances page in HCL OneTest™ Server. You can view the details, configuration settings, routing rules, usage statistics, or logs of a specific running instance of the virtual service. You can also stop the running instance.
  - Viewing configurations of running instances of virtual services
    After you start virtual services from the Resources page, you can view the details, configuration settings, routing rules, usage statistics, or logs of a specific running virtual service instance from the Instances page on HCL OneTest™ Server.
  - Modifying configurations of running instances of virtual services
    After you start virtual services from the Resources page and before you run tests on the virtual service, you might want to modify the configurations for the behavior or the logging level of the running instance.
  - Viewing routing rules of the virtual services
    When you run virtual services that are created to run on proxies or intercepts and have routing rules defined, you can view the proxies or intercepts and the routing rules from the Intercept Rules page.
  - Viewing usage statistics of virtual services
    After you start stubs or virtual service resources that are in the project repositories, and then run tests on the virtual service, you can view the usage statistics of the virtual services from the Usage page on HCL OneTest™ Server.
  - Stopping a virtual service
    When you want to stop a virtual service instance that is running in HCL OneTest™ Server, you can stop the running virtual service from the Instances page.
- Test results
  After the tests or schedules are run and completed, you can view the results and 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 service
  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. The Resource Monitoring service in HCL OneTest™ Server helps you monitoring the resources of a system and establish the performance metrics 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.
- Integrating 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 the server
  Desktop clients and third-party integrations use offline user tokens to connect to HCL OneTest™ Server.

Prerequisites for running HTTP virtual services

You can find information about the tasks that you must complete before you configure a run of the HTTP virtual services on HCL OneTest™ Server.

Conditions for running of HTTP virtual services

Before you run the HTTP virtual services from HCL OneTest™ Server, you must check for the following conditions and perform the actions indicated:


If...	Then...
You want to route the HTTP traffic via the HTTP proxy either to the virtual service or live systems, based on routing rules.	You must set up the HTTP proxy. See Setting up the HTTP proxy.
You are working with HCL OneTest™ Server V10.1.3, which is installed on Ubuntu.	HTTP virtual services are exposed via host names are of the following form: in-<unique_id>.<INGRESS_DOMAIN> Note: The DNS used by a computer that runs a client application or the HTTP proxy that routes traffic to the virtual service needs to resolve such host names to the IP address of the ingress domain. You must perform the following actions that depend on the method you have used to set up the ingress domain: If you used `nip.io` to form the ingress domain, then that virtual services host names are automatically resolved to the IP address of the ingress domain. For example, if you used `nip.io` to form the ingress domain as follows: 10.1.2.3.nip.io The virtual services host names are resolved by `nip.io` to the IP address as `10.1.2.3`. If your ingress domain does not use `nip.io` then you must ensure that the DNS in use by the client application or the HTTP proxy can resolve host names of the virtual services to the IP address of the ingress domain. For example, if the ingress domain is as follows: `myhost.mycom.com` The DNS must resolve `*.myhost.mycom.com` to the IP address of `myhost.mycom.com`.