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.
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.

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 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.
- 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 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 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 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.
  - Test results and reports overview
    Rational® Test Automation Server is a single location for hosting the results and reports of all tests run on different desktop clients and for tests run from the server.
- 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.
- 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.
- 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.

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.

From the Results page, you can perform the following tasks:

Searching for test results. You can filter test results by using any of the following ways:
- By using the Search field to search for results by name.
- By selecting predefined time interval from the Selection interval drop-down list.
- By selecting To and From date from the Date Interval option.
- By clicking verdict from the Verdict summary slider (Pass, Fail, Inconclusive, or Error).
- By creating filter queries.
Adding labels if you have a tester or an owner role.
Locking test results: Locked results can be unlocked by the project owner or the project member who locked the results.
Deleting test results.
Comparing performance reports.
Viewing trending reports.
Viewing multiple reports depending on the test types: Statistics reports, Mobile and Web UI reports, Functional reports, Unified Reports, or HTML reports generated from Postman or JMeter test runs.
Re-executing tests with the same commit id.
For more details, see the links in the next section of this page.