Suites and tests that are supported on Rational® Test Automation Server

You can find information about the types of Test Suites and tests that you can configure for a run in a project on Rational® Test Automation Server.

The following table lists the Test Suites and test types that are supported and those tests that are not supported to run on Rational® Test Automation Server:
Supported Suites Supported tests Unsupported tests
  • Accelerated Functional Testing (AFT) Suites
  • Compound Tests that contain any of the following types of tests:
    • Web UI tests
    • HTML tests
    • Mobile tests
  • Functional Web UI tests
  • Functional Windows tests
  • Functional Mobile tests
  • Traditional HTML tests
  • Traditional non-HTML tests
  • API Suites that include the following Test Suites:
    • Test Suites that contain scenarios with references to local stubs.
    • Test Suites that contain stubs that virtualize services run in any Kubernetes cluster or in the Kubernetes cluster that hosts Rational® Test Automation Server.
  • Stubs

API tests

Suites or tests with subscribe actions that operate in the watch mode.
  • Compound Tests that contain performance tests
  • Rate Schedules
  • VU Schedules

Performance tests
  • A single test script of any test extension.
  • Tests that belong to 32-bit test extensions and SOA Quality included in VU Schedule, Rate Schedule, and Compound Test.
  • Citrix, SAP, or Siebel as an individual test or as part of a Compound Test.
Note: You must create compound tests for the same type of tests. For example, you can create a compound test that has different mobile tests that use different mobile testing platforms.
Restriction: You cannot merge folders that contain different test projects in the same project directory. For example, you cannot create a project directory that contains a Performance test project and an API Suite project. You must create separate project directories for each test type. For example, you must create the Performance test in the project directory as /MyPerfProject/ and the API Suite in the project directory as /MyAPIProject, before you commit the projects to the remote repository.