Home
Test Author guide
As a test author, you are responsible to create test scripts and enhances them by applying different test elements such as dataset, variables, and verification points.
Testing in the UI Test perspective
When you develop web applications, Windows-based applications, or mobile applications, you can use IBM® Rational® Functional Tester to create functional tests for these applications. You must first record the tests and then use Rational Functional Tester to run the tests before you can view the test results.
Compound tests
You can create compound tests to help you organize smaller tests into scenarios that can then be run end-to-end. You can combine tests from different extensions to achieve end-to-end flow.
Creating a compound test
You can create compound tests to help you organize smaller tests into scenarios that can then be run end-to-end. You can combine tests from different extensions to achieve end-to-end flow.

Test Author guide
As a test author, you are responsible to create test scripts and enhances them by applying different test elements such as dataset, variables, and verification points.
- Testing in the UI Test perspective
  When you develop web applications, Windows-based applications, or mobile applications, you can use IBM® Rational® Functional Tester to create functional tests for these applications. You must first record the tests and then use Rational Functional Tester to run the tests before you can view the test results.
  - Testing web applications
    You can test web applications in Rational® Functional Tester by using the industry-standard browsers such as Google Chrome, Apple Safari, Mozilla Firefox, and Microsoft Edge. You can record Web UI tests and then play back the tests to evaluate the test results. You can also test the web applications on dual monitors when you extend the display of your computer to a secondary monitor.
  - Testing mobile applications
    You can test the Android or iOS mobile applications by recording and playing back mobile tests on Android devices or emulators, iOS mobile devices or simulators by using Rational® Functional Tester.
  - Recording SAP tests
    When you record a test, the test creation wizard records your interactions with the SAP server, generates a test from the recording, and opens the test for editing. You can record tests from the SAP GUI. You can also record SAP batch input tests that can be used to produce a heavy load on the server while minimizing the processing requirements for virtual testers.
  - Working with Selenium or Appium tests
    You can manage your Selenium or Appium Java™ tests from the Web UI Test perspective, where you can import and modify the tests, add them to compound tests, and run them. You can also create new Appium Java tests from the Perfecto perspective on Windows™ and Mac OS, add the tests to compound tests, and run them. Perfecto is not currently supported on Linux®.
  - Compound tests
    You can create compound tests to help you organize smaller tests into scenarios that can then be run end-to-end. You can combine tests from different extensions to achieve end-to-end flow.
    - Creating a compound test
      You can create compound tests to help you organize smaller tests into scenarios that can then be run end-to-end. You can combine tests from different extensions to achieve end-to-end flow.
    - Viewing compound tests
      You can view a compound test in the Compound Test Editor.
    - Adding tests into a compound test
      After creating a compound test, you can add the smaller test pieces that contribute to the larger workflow you are constructing with the compound test. When you run a compound test, each of the tests added to it are invoked in the sequence defined.
    - Modifying a compound test
      You can modify a compound test in the Compound Test Editor.
    - Running compound tests
      When you run a compound test, its test elements are run in the order defined in the compound test.
    - Generating compound test result reports
      When a compound test run is completed, a Test Log is shown in the Test Execution perspective. You can work with the information in the test log and also generate test result reports.
    - Adding a compound test to a Test Workbench project
      You can create a compound test in a test workbench project. If you have an existing compound test, you can import the test to a test workbench project.
  - Accelerated Functional Tests
    When you create Web UI, mobile, or Windows tests, you can use the Accelerated Functional Test (AFT) feature in Rational® Functional Tester to distribute test effort during the play back of the recorded tests.
  - Working with keywords
    In Rational® Functional Tester, you can record and then associate Test Workbench tests with the keywords that are created in IBM® Rational Quality Manager. The keywords are used in manual tests in Rational Quality Manager. When you run a manual test that contains a keyword associated with a Rational Test Workbench test, the Test Workbench test is run on the workstation where the adapter has been started.
- Testing in the Functional Test perspective
  When you develop Java, HTML, or Terminal-based applications, you can use IBM® Rational® Functional Tester to create traditional functional tests for these applications. You must first record the tests and then use Rational Functional Tester to run the tests before you can view the test results.
- Extending the UI Test perspective with custom code
  You can use custom code to extend the default Web UI testing capabilities. You can write custom Java™ code and call the code from the test. You can also specify that results from the tests that are affected by your custom code to be included in reports.
- Extending the Functional Test perspective
  You can use custom code to extend the default functional testing capabilities. You can write custom code and call the code from the test. You can also specify that results from the tests that are affected by your custom code to be included in reports.
- Experimental Features
  Rational® Functional Tester contains a set of pre-releases that enable you to test various experimental features. These experimental features, while still in progress, are introduced early in the release to seek your feedback on its overall functionality and performance. You can play around with these capabilities before they are made available and supported as a general feature in an upcoming release.

Creating a compound test

You can create compound tests to help you organize smaller tests into scenarios that can then be run end-to-end. You can combine tests from different extensions to achieve end-to-end flow.

Procedure

Create a test workbench project.
In the Web UI Test perspective, in the Test Navigator, right-click the test workbench project and click New, and then click Compound Test.
In the New Compound Test dialog box, specify the name of the compound test and the location where it must be stored. By default, the test is stored in the workspace of the test workbench project you selected. You can select a different project location if desired.
The file extension testsuite is added to the file name, and the new compound test is added to the Compound Tests folder of the test workbench project, visible in the Logical View. The new test is also visible in the Resource View, under the test workbench project. The contents and test element details are displayed in the compound test editor in the right panel.
In the compound test editor, add the components of the compound test.

The types of tests you can combine into a compound test depend on the testing requirements and on the components that you have licensed. For example, if you have the appropriate licenses, you can add Web UI tests, performance tests, mobile web tests, and functional tests into a compound test.
To build the scenario you require in a compound test, you can also add the following annotations by clicking Add and selecting the appropriate option:
- Comments
- Synchronization points
- Loops
- Delays
- Transaction folders
- Tests that are mandatory, using the Finally blocks
- Tests to be run in random order, using the Random Selector
Save your changes.