Test run considerations for API Suites

Before you configure an API Suite run, you must read the considerations you must take into account.

You can find the following information about API Suites:

Important information about API Suites

When you want to run an API Suite from a project on Rational® Test Automation Server and the Test Suite in Rational® Integration Tester meets any of the following conditions:
  • The Test Suite refers to local stubs.
  • The transport used in the tests in the Test Suite is configured with the host name set to localhost for the HTTP/TCP proxy.
  • The Test Suite has tests that use a transport and the transport requires third-party application Jar files for a successful run.
You must then refer to the following table for the next steps:
If... Then...

The tests in an API Suite refer to local stubs.

You must remove the local stubs referenced in the tests or published the stubs to Rational® Test Control Panel before you commit the test asset to the remote repository.

To publish and edit stubs, see Publishing stubs.

The transport used in the tests in an API Suite is configured with the host name set to localhost for the HTTP/TCP proxy.

You must replace the host name with fully-qualified-domain-name or IPAddress of the proxy host in the tests before you commit the test asset to the remote repository.
You plan to run the API Suite on the computer where Rational® Test Automation Server is installed. The API Suite contains tests that use a transport from any of the following third-party applications:
  • Camel
  • CentraSite
  • CICS
  • Coherence
  • Database
  • IMS
  • Integra
  • JMS
  • SAP RFC
  • Software AG Universal Messaging
  • TIBCO EMS
  • TIBCO Rendezvous
  • TIBCO SmartSockets
  • WebSphere Application Server Service Integration Bus (SiBus)
  • WebLogic
  • Software AG webMethods
  • WebSphere MQ
You must complete the following tasks:
  • Identify the location of the third-party application JAR files. You can use Library Manager to know the location where the third-party application JAR files are saved.
  • Copy the third-party application JAR files to the computer where Rational® Test Automation Server is installed.
See Copying third-party application Jars to Kubernetes.
You plan to run the API Suite on a remote Docker host. The API Suite contains tests that use a transport from any of the following third-party applications:
  • Camel
  • CentraSite
  • CICS
  • Coherence
  • Database
  • IMS
  • Integra
  • JMS
  • SAP RFC
  • Software AG Universal Messaging
  • TIBCO EMS
  • TIBCO Rendezvous
  • TIBCO SmartSockets
  • WebSphere Application Server Service Integration Bus (SiBus)
  • WebLogic
  • Software AG webMethods
  • WebSphere MQ
You must complete the following tasks:
  • Identify the location of the third-party application JAR files. You can use Library Manager to know the location where the third-party application JAR files are saved.
  • Copy the third-party application JAR files to the computer where the remote Docker host is installed.
See Copying third-party application Jars to a remote Docker host.

Important information about report configuration in API Suites

Rational® Integration Tester Test Suites must be configured to use a results database so that the details of the test results can be captured and displayed in the Rational® Test Automation Server API results reports. If you have such API Suites, you must have configured a results database in the project used in Rational® Integration Tester. See Configuring the project results database.

If your server projects use either a Microsoft SQL Server, MYSQL, or both as a project results database, you must copy the Microsoft SQL Server and MySQL database JAR files to the JDBC folder in the path /data/JDBC on IBM® Rational® Test Automation Server. See Copying third-party application Jars to Kubernetes.

The database JAR files that you need are based on the version of Microsoft SQL Server or MQSQL that you using with Rational® Integration Tester. See Adding Microsoft SQL Server and MySQL drivers.

For running an API Suite, see Configuring a run for an API Suite.