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.
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.
Publishing changes to the system model
When you create, delete, or modify components in a system model, the changes are saved locally and are not visible to the other project members or team space members. You must publish the system model changes to the team space repository to make your changes visible for all users of the team space.

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.
  - Task flows for working with a system model
    You can find information about the tasks that you can perform when you want to create a system model, create components, associate the components, create linkages among the components, and then publish the system model to the team space repository. Also, you can find information about the tasks that you must perform when you want to modify an existing system model.
  - Adding a repository to a team space
    You must add a repository to the team space when you want to create, modify, or store a system model.
  - Creating a system model
    Before you can create components in a system model, you must create an empty system model and publish the system model to the team space repository.
  - Creating components
    The first step in building a system model is to create components. The components serve as the building blocks for the system model.
  - Creating child components
    You can create components as children of existing components in the system model.
  - Creating linkages between components
    You can create linkages between components that display the relationship between them. The linkages can be between components or between child components of the same or different parent components.
  - Deleting linkages between components
    When you do not want to retain the linkages between components that you created in the system model, you can delete the linkages.
  - Modifying components
    At any point in time, after you create a component, you can modify and update the details of the components such as the component type, and the relationships with other components.
  - Deleting components
    When you do not require a component, you can delete the component.
  - Publishing changes to the system model
    When you create, delete, or modify components in a system model, the changes are saved locally and are not visible to the other project members or team space members. You must publish the system model changes to the team space repository to make your changes visible for all users of the team space.
  - Associating resources with components
    After creating components in the system model, you can navigate to a project in the team space to associate the Suites, tests or virtual service resources in the project repositories with the components in the system model.
  - Viewing resources associated with components
    After you associate Suites and Tests or virtual services resources with components in the system model, you can view the associated resources from the System Model page. You can opt to start an instance of the associated resource or stop a running instance of the associated resource.
  - Removing resources associated with components
    When you do not want to retain the resource that you associated with a component, you can delete the resource in the system model.
  - Publishing changes of associating resources with components
    After you associate resources in a project with a component in the system model, you must publish the changes made to the branch in the project repository, if you want the associations to be visible to the other members in the project.
  - Viewing the system model
    You can view an existing system model or you can create a system model if a system model does not exist on the System Model page.
  - Deleting a system model
    When you want to remove an existing system model to create a new system model, you can delete the existing system model.
  - Deleting a repository that is added to a team space
    You can delete a repository that you added to the team space when you do not want to use a team space repository.
- 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 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.

Publishing changes to the system model

When you create, delete, or modify components in a system model, the changes are saved locally and are not visible to the other project members or team space members. You must publish the system model changes to the team space repository to make your changes visible for all users of the team space.

Before you begin

You must have completed the following tasks:

Created and published the system model. See Creating a system model.
Performed actions to add or modify the system model that you want to publish.

Procedure

Log in to Rational® Test Automation Server.
Open the team space to which a team space repository is added.

The Active projects page is displayed.
Click System Model on the left navigation pane.

The System Model page is displayed.
View the uncommitted changes made to the system model that is displayed along with the See unpublished commits icon .
Click the See unpublished commits icon , and then select the Publish changes option.

Note: If you do not want to commit the changes that you made to the system model, you can select the Discard changes option.
Enter a commit message in the Description of change field, and then click Publish.

Results

You have published the changes that you made in the system model to the team space repository. Other members of the team space can now view and use the system model.