Release Notes for IBM® Rational® Test Automation Server

This document includes information about What’s new, installation and upgrade instructions, known issues, and contact information of IBM Customer Support.

Contents

Description

Rational® Test Automation Server is a server that includes capabilities such as project and role-based security, Docker-based distribution and installation, and running of test cases. For more information about the server, see IBM Rational Test Automation Server overview.

What's new

The following sections list the new features, enhancements or other changes made in this release.

  • Installation

  • Test runs

    • Support for running Compound Tests that contain mobile tests

      You can now configure a run for a Compound Test that contains mobile tests and then run the Compound Test on Rational® Test Automation Server. See Configuring a run of a Compound Test that contains mobile tests.

    • Overriding Resource Monitoring settings in a performance schedule

      Now in the Execution dialog, the Resource Monitoring tab displays the settings related to the Resource Monitoring sources and labels as they were set in the performance schedule. This information is helpful to decide whether you want to override them with the Resource Monitoring sources that are available in your Server project, or not. See Controlling Resource Monitoring sources in a schedule.

  • Service virtualization: Tech Preview

    • Virtualizing a service in a namespace of Rational® Test Automation Server

      Previously, you specified the short name of a service that you wanted to virtualize as the host for the HTTP transport and specified the namespace in the recording settings for an Istio proxy. For example, to record the reviews service that had an FQDN of reviews.default.svc.cluster.local the host for the HTTP transport to be specified was reviews, and the namespace to be specified for the Istio Proxy was default. However, Istio routing in Rational® Test Automation Server only uses the host name and port to generate the routing rule and for stubbing. Therefore, the host name must contain the namespace so that Rational® Test Automation Server can correctly identify the service that is being stubbed.

      Now, you can enable Rational® Test Automation Server to use the namespaces that you want by providing the namespaces at the time of the installation of the server software. See Prerequisites for running Istio stubs that virtualize services in Rational Test Automation Server.

  • Test authoring

    • Saving a copied dataset

      You can now save a copy of a dataset in a different folder or make a copy with a different name, by using the Save As option. See Datasets overview.

    • Displaying icons to view who is editing datasets

      In Rational® Test Automation Server, you can now see all members who are editing a particular dataset. See Editing a dataset.

Known issues

You can find information about the known issues identified in this release of Rational® Test Automation Server.

Known problems are documented in the download document for each product and in the form of individual technotes in the Support Knowledge Base:

Table 1. Download documents and technotes
Product Download document Knowledge base
Rational® Test Automation Server Release document Knowledge articles

The knowledge base is continually updated as problems are discovered and resolved. By searching the knowledge base, you can quickly find workarounds or solutions to problems.

Contacting IBM Rational Software Support

  • For contact information and guidelines or reference materials that you might need when you require support, read the IBM Support Guide.

  • For personalized support that includes notifications of significant upgrades, subscribe to Product notification.

  • Before you contact IBM Rational Software Support, you must gather the background information that you might need to describe your problem. When you describe a problem to an IBM software support specialist, be as specific as possible and include all relevant background information so that the specialist can help you solve the problem efficiently. To save time, know the answers to these questions:
    • What software versions were you running when the problem occurred?
    • Do you have logs, traces, or messages that are related to the problem?
    • Can you reproduce the problem? If so, what steps do you take to reproduce it?
    • Is there a workaround for the problem? If so, be prepared to describe the workaround.