Rational® Integration Tester and Rational® Test Automation Server

You can publish test reports for tests run on Rational® Integration Tester to Rational® Test Automation Server. You can create secrets collections for your project and store them securely on Rational® Test Automation Server that you can retrieve the secrets from Rational® Test Automation Server during tests at runtime.

The secrets collections in Rational® Test Automation Server project have a separate access control list managed by the project owner. Earlier to 9.5.0, the secrets were stored in tags as an environment property in Rational® Integration Tester and they were visible to anybody who could see the project.

Rational® Test Automation Server

Rational® Test Automation Server is a new combined server that includes capabilities such as Docker-based distribution, installation, and execution of test cases.

You must set up access to Rational® Test Automation Server so that you can perform the following operations:
  • Publishing test suite reports to a project on Rational® Test Automation Server. For more information, see Publishing test results to Rational Test Automation Server.
  • Retrieving the stored secrets from a project configured in Rational® Test Automation Server for using the secrets in tests at runtime.

With the introduction of secrets (under secrets collections) for a project in Rational® Test Automation Server, managing access to separate environments is simplified. If a member of a project does not have access to a secret (for example, a server credential), then the member cannot accidentally or maliciously run tests against that server. For example, tests that require accessing the database server by using the server credentials to retrieve stored data can be executed by a member if the access to the secrets is enabled.

If the secrets are not stored on Rational® Test Automation Server, you must then store secrets as plain text as an environment property in Rational® Integration Tester. This means that a user can accidentally run a test against the wrong environment.

You can perform the following tasks for your project that you want to test after you have set up Rational® Test Automation Server:
  • As a project owner, you can configure a project in Rational® Test Automation Server for creating secrets collections. Secrets are key-value pairs that are created for your project in Rational® Test Automation Server under a secrets collection.
  • You can decide to grant or restrict access to members in your organization to the secrets collections. Controlling access to secrets means controlling access to applications and systems under test. Members with access can access the secrets collection in Rational® Test Automation Server and use the secrets in test runs in Rational® Integration Tester.
  • Members of Rational® Test Automation Server project must generate offline user tokens from the Rational® Test Automation Server and use the offline user token for gaining access to Rational® Test Automation Server. See Generating an offline user token.
  • Members can access Rational® Test Automation Server from Rational® Integration Tester. See Accessing Rational Test Automation Server.
  • Members across the organization can retrieve the stored secrets from Rational® Test Automation Server for using the secrets in test runs in Rational® Integration Tester without the necessity to store the secrets as visible environment tags in their project in Rational® Integration Tester. See Retrieving secrets from Rational Test Automation Server.