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 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 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 IBM® Rational® Test Automation Server. You must then add the registered remote Docker host to your project before you can run tests on the remote Docker host location.
Viewing remote Docker hosts that are registered with IBM® Rational® Test Automation Server
You must register the remote Docker host in your team space with Rational® Test Automation Server before you add the remote Docker host to your project in that team space, which contains the test assets that you want to run on the remote Docker host.

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 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 run a test asset in a project on Rational® Test Automation Server, you must read the information about the different tests assets. You can add a remote static agent or Docker host 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 the agents that you must install on remote computers and configure the agents to register with IBM® Rational® Test Automation Server. After the agents are registered, you can add them to your projects and then select them as locations to run tests.
- 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 IBM® Rational® Test Automation Server. You must then add the registered remote Docker host to your project before you can run tests on the remote Docker host location.
  - Test run considerations for running tests on remote Docker hosts
    Before you can configure a test to run on a remote Docker host, you must read the considerations that you must take into account.
  - Setting up a remote Docker host
    You must set up a computer to host the remote Docker host. You can set up the remote host with a non-secure mode of connection with IBM® Rational® Test Automation Server.
  - Setting up a secure remote Docker host
    You must set up a computer to host the remote Docker host. You can set up the remote host with a secure mode of connection with IBM® Rational® Test Automation Server by using certificates issued by the remote host computer that authenticate the connection.
  - Copying third-party application Jars to a remote Docker host
    You can run API Suites in a project on Rational® Test Automation Server on a remote Docker host. If the API Suites use a transport and the transport requires third-party Jar files for a successful run, you must ensure that the third-party application Jar files are available at the test run time. To achieve this, you must copy the third-party application Jar files to the computer where you have set up the remote Docker host.
  - Registering a remote Docker host
    You must register the remote Docker host with Rational® Test Automation Server before you add the remote Docker host to your project in a team space, which contains the test assets that you want to run on the remote Docker host.
  - Viewing remote Docker hosts that are registered with IBM® Rational® Test Automation Server
    You must register the remote Docker host in your team space with Rational® Test Automation Server before you add the remote Docker host to your project in that team space, which contains the test assets that you want to run on the remote Docker host.
  - Adding a remote Docker host
    You can choose to run tests on Docker hosts that you have set up on remote host computers. You must register the Docker host with IBM® Rational® Test Automation Server and then add them to your project before you run tests on the remote Docker hosts.
  - Editing configurations
    You can edit the host name or the port of the registered Docker host computer instead of registering it as a new remote host if any of the parameters are changed on the remote host computer. You can also change the mode of authentication of a registered remote Docker host.
  - Deleting a remote Docker
    You can delete a remote Docker host that you added to your project in IBM® Rational® Test Automation Server when you no longer need it to run tests.
  - Unregistering a remote Docker host from IBM® Rational® Test Automation Server
    You can unregister a remote Docker host that is registered with Rational® Test Automation Server in a team space when you no longer require it.
- Test run configurations
  You can configure and run tests in IBM® Rational® Test Automation Server after you add the test resources to your project in your team space.
- 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 virtual services that are connected to Rational Test Automation Server. You can view the routing rules and usage statistics of virtualized services, agents, or intercepts that are connected to Rational Test Automation Server.
- Test results
  After the tests, Suites, or schedules are run and completed, you can view the results and open the 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
  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 Rational® Test Automation 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 Rational® Test Automation 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 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.

Viewing remote Docker hosts that are registered with IBM® Rational® Test Automation Server

You must register the remote Docker host in your team space with Rational® Test Automation Server before you add the remote Docker host to your project in that team space, which contains the test assets that you want to run on the remote Docker host.

Before you begin

Depending on the mode of connection with Rational® Test Automation Server, you must have set up the remote Docker host computer either for a secured mode or for an unsecured mode of connection. See Setting up a remote Docker host computer or Setting up a secure remote Docker host computer.

Procedure

Log in to Rational® Test Automation Server.

The team space that contains your project is displayed.
Click Infrastructure > Agents and Intercepts in the navigation pane.

The Agents and Intercepts page is displayed.

You can view the agents, intercepts or Dockers that are registered with Rational® Test Automation Server in your team space.
You can view the Dockers that you own in any of the following ways:
- Search for the Docker by entering the name of the Docker host in the Search field.
  Note: You can enter either the full name or any text that is in the name. The search is enabled for case sensitive text that you can enter.
- Sort the Type column to sort the items and then identify the Docker by the name displayed.
- Sort the Agents column to sort the items and identify the Docker by the owner.
You can view the following details about the Dockers that are registered with Rational® Test Automation Server in the team space:
- The projects in the team space to which the Docker host is added, are displayed in the Projects column.
- The status of the Docker host is displayed in the Status column.
  Note: You can add Docker hosts that are in the Ready state to your project, and then use them as locations to run tests.

Results

You have viewed the remote Docker hosts that are registered with Rational® Test Automation Server in your team space.

What to do next

You must add the registered remote Docker host to your project in your team space before you use the remote Docker host as a location to run tests in your project. See Adding a remote Docker host to the project for running tests.