Home
Test Execution Specialist Guide
This guide describes tasks that you must complete before you can configure and run tests in Rational® Test Automation Server. You can 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 Rational® Test Automation Server. You can start or stop the stubs connected to Rational Test Automation Server. You can view the stub usage statistics and the routing rules configured for the stubs, agents, or proxies that are connected to Rational Test Automation Server.
Prerequisites for running stubs
You can find information about the prerequisite tasks that you must complete before you can run stubs on Rational® Test Automation Server.
Prerequisites for running HTTP stubs
You can find information about the tasks that you must complete before you run HTTP stubs on Rational® Test Automation Server.

Test Execution Specialist Guide
This guide describes tasks that you must complete before you can configure and run tests in Rational® Test Automation Server. You can 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 configure and run a test in a project on Rational® Test Automation 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 set up dedicated external Docker hosts to run large tests or run tests remotely to free up the dependency of running tests on the default cluster of IBM® Rational® Test Automation Server.
- Test run configurations
  You can configure and run tests in IBM® Rational® Test Automation 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 Rational® Test Automation Server. You can start or stop the stubs connected to Rational Test Automation Server. You can view the stub usage statistics and the routing rules configured for the stubs, agents, or proxies that are connected to Rational Test Automation Server.
  - Prerequisites for running stubs
    You can find information about the prerequisite tasks that you must complete before you can run stubs on Rational® Test Automation Server.
    - Prerequisites for running HTTP stubs
      You can find information about the tasks that you must complete before you run HTTP stubs on Rational® Test Automation Server.
    - Prerequisites for running Istio stubs that virtualize services in Rational® Test Automation Server
      You can find information about the tasks that you must complete before you run Istio stubs that virtualize services in Rational® Test Automation Server.
    - Setting up the HTTP proxy
      When you want to run stubs on Rational® Test Automation Server, you can set up an HTTP proxy to route requests to the stubs. You must configure the HTTP proxy with the Rational Test Automation Server URL and offline user token generated from Rational Test Automation Server so that the HTTP proxy can register with Rational Test Automation Server.
  - Starting a stub
    When you have stubs in the API test assets, you can start the stubs contained in the API test assets from the Execution page in IBM® Rational® Test Automation Server.
  - Working with HTTP stubs without using proxies
    When you run the HTTP stubs on Rational® Test Automation Server, the endpoint on which the stub is exposed externally uses a host name that includes a generated ID. If a client application is required to call the stub 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 stub.
  - Viewing routing rules
    When stubs are created to run on agents or proxies, or have routing rules defined, and you run such stubs on Rational® Test Automation Server, you can view the agents, proxies, or the routing rules from the Routing Rules page.
  - Viewing stub usage statistics
    After you start stubs that are connected to Rational® Test Automation Server, and then run tests on the stub, you can view the stub usage statistics from the Stub Usage page on Rational Test Automation Server.
  - Stopping a stub
    When you want to stop a stub that is running in IBM® Rational® Test Automation Server, you can stop the running stub from the Progress page. You must stop a running stub after you have completed running tests that are used by the stub.
- Test results
  After the tests or schedules are run and completed, you can view the results and reports in IBM® Rational® Test Automation 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 Rational® Test Automation 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.
- Integration with Jira as a defect management system
  You can integrate Jira as a defect management system with your project on IBM® Rational® Test Automation Server to create defects for the tests that are available in the project after the test run is complete.
- Integrating with other applications
  You can integrate certain applications with IBM® Rational® Test Automation 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 Rational® Test Automation Server.

Prerequisites for running HTTP stubs

You can find information about the tasks that you must complete before you run HTTP stubs on Rational® Test Automation Server.

Conditions for running of HTTP stubs

Before you run the HTTP stubs from Rational® Test Automation 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 stubs or live systems, based on routing rules.	You must set up the HTTP proxy. See Setting up the HTTP proxy.
You are working with Rational® Test Automation Server V10.1.2 installed on Ubuntu.	HTTP stubs are exposed via host names as the default action and 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 stubs can resolve such host names to the IP address of the ingress domain. You must perform the following actions that depend on the way you have set up the ingress domain: If you used nip.io, to form the ingress domain, then that stub 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 Then the stub host names are resolved by nip.io to the IP address as 10.1.2.3. If you did not use nip.io to form the ingress domain, then you must ensure that the DNS in use by the client application or the HTTP proxy resolves the ingress domain to the IP address of the ingress domain. For example, if the ingress domain is of the following form: *.<INGRESS_DOMAIN> Then the host name must resolve to the <INGRESS_DOMAIN_IP_address>.