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.
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.
Test run considerations for JUnit tests
Before you can run JUnit tests on IBM® Rational® Test Automation 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 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.
  - 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 IBM® Rational® Test Automation 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 IBM® Rational® Test Automation 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 IBM® Rational® Test Automation 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 that you install on remote computers and then configure the remote 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.
- 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 IBM® Rational® Test Automation 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 IBM® Rational® Test Automation Server after you add the test resources to your project in your team space.
- Configuration of a scan of an application code
  You can use Rational® Test Automation 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 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.
- Working with IBM® Rational® Test Automation Server REST services
  When you want to use the IBM® Rational® Test Automation Server REST APIs in your test automation scripts, you can view the REST APIs that are exposed by IBM Rational Test Automation Server. You can also run the APIs from within your project in IBM Rational Test Automation Server.

Test run considerations for JUnit tests

Before you can run JUnit tests on IBM® Rational® Test Automation Server, you must read the considerations that you must take into account and complete the tasks indicated.

When you want to run JUnit tests, you must have completed the following tasks:

You must ensure that the JUnit extension on IBM® Rational® Test Automation Server is enabled at the time of installation of the server software or is running before you add the repository that contains the JUnit tests to the server project. See Prerequisites for installing the server software on IBM Red Hat OpenShift or Prerequisites to install the server software on Ubuntu.
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 plugin, 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.