Release notes for IBM® Rational® Service Tester for SOA Quality

This document contains information about what's new, installation instructions, known problems in IBM® Rational® Service Tester for SOA Quality and contact information of IBM Customer Support.

Contents

Product description

The service testing capabilities of Rational® Service Tester for SOA Quality automate the creation, execution, and analysis of functional, regression and performance tests for SOAP-based web services. The SOAP-based web services includes support for Java Messaging Service (JMS), WebSphere MQ, WebSphere Java MQ, and Microsoft .NET Windows Communication Foundation (WCF), and any service that produces XML, plain text, or binary data.

What's new

  • Support to the latest version of the SAP GUI client

    You can now record and play back tests of SAP applications built with the SAP GUI client V7.7.

  • Using a JSON notation in a reference for an HTTP test

    If a request or a response contains the JSON data, then the test editor displays a value in a more readable JSON format. If you create a reference in the JSON data, you can now use the JSON notation instead of a regular expression to locate the JSON value at run time. See Creating a reference or field reference.

  • Support for application performance management tools

    You can now use the Dynatrace application with Rational® Performance Tester to enhance the data collection by adding filters based on HTTP headers that you used in tests. See Using Application Performance Management in a schedule.

  • Support to record tests by using the Microsoft Edge browser

    After you install Rational® Performance Tester either on Windows systems or Mac operating systems, you can now choose the Chromium-based Microsoft Edge browser to record the following tests:
    • HTTP tests

    • Citrix tests from the Citrix Web Interface

    • SAP tests when initiated from HTTP SAP-portal

    • Service tests when recorded from a browser

    See Recording an HTTP test.
  • Bug fixes

    Fixed customer-reported and internally found defects.

Installing the product

To download the product from IBM® Passport Advantage®, you must follow the instructions provided in the download document at Rational® Service Tester for SOA Quality V10.2.0.

For installation instructions, see Installing IBM Rational Service Tester for SOA Quality.

Remember:
  • You cannot upgrade to the latest version of the product. You must first uninstall the existing version of the product before you install the latest version of the product.

  • After you install Rational® Service Tester for SOA Quality V10.2.0, at any point in time if you want to use the previous version of the product, you cannot roll back to the previous version. If you want to use the previous version of the product, you must uninstall the existing version, and then install the required version of the product.

Known issues

Known problems are documented in the download document and in the form of individual technotes in the Support Knowledge Base. See IBM Support Knowledge Base. The knowledge base is continually updated as issues are discovered and resolved. By searching the knowledge base, you can quickly find workarounds or solutions to issues.

Product Download document Knowledge Base

Rational® Service Tester for SOA Quality

IBM support

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.