Home
Rational® Functional Tester
Tutorials
This section contains the tutorials which explains the main features of HCL OneTest™ UI.
Tutorials for testing in the UI Test perspective
You can use the tutorials to get started with testing in the UI Test perspective in Rational® Functional Tester.
Lesson 5: Modularize the test script
In this tutorial, you recorded a test scenario in which you signed in to the web site, browsed for a product, and saw pricing details. In the actual scenario, you would have also recorded how to purchase, check out the product, and sign out of the website. You would have done that to avoid recording the same application multiple times. However, maintaining a big test script with a lot of data can be difficult. After the recording, you can modularize the test script by splitting it at appropriate steps and thereby creating meaningful chunks of test scripts. For example, for the test scenario in this tutorial, you can split the ‘Sign in’ and ‘Choosing the product’ steps and create two test scripts out of it. You can then add these scripts to a Compound Test to run in sequence.

Rational® Functional Tester
- Release Notes
  This document contains information about new features, system requirements, and known limitations in HCL OneTest™ UI.
- Getting Started Guide
  This guide provides an overview of Rational® Functional Tester. You can find the task flows to get you started with Rational Functional Tester. This guide is intended for new users.
- Tutorials
  This section contains the tutorials which explains the main features of HCL OneTest™ UI.
  - Tutorials for testing in the UI Test perspective
    You can use the tutorials to get started with testing in the UI Test perspective in Rational® Functional Tester.
    - Lesson 1: Recording a test scenario
      With the Web UI Test perspective, you can initiate the recording of a specific test scenario on your web application. Typically, you would create smaller test scenarios for better maintenance. When you start a recording, HCL OneTest™ UI automatically captures the actions that you do on the web application. To ensure that the recorder captures each action correctly, wait till the web pages are loaded completely. You can later remove this extra ‘waiting time’ (Think time) that is spent in the recording when you play back a test. After you stop the recording, the test is generated.
    - Lesson 2: Adding a verification point
      In this lesson, you will learn how to add a verification point to a test step.
    - Lesson 3: Running the test
      After modifying the test script, you can now run the test to check if the test scenario is played back successfully.
    - Lesson 4: Viewing test results
      The reports display whether the test run was successful. The Mobile and Web UI report is the primary report for a Web UI test. It displays each of the steps with the screenshot of the UI and the overall response time. If a test run fails, the error message is displayed against the step in the report.
    - Lesson 5: Modularize the test script
      In this tutorial, you recorded a test scenario in which you signed in to the web site, browsed for a product, and saw pricing details. In the actual scenario, you would have also recorded how to purchase, check out the product, and sign out of the website. You would have done that to avoid recording the same application multiple times. However, maintaining a big test script with a lot of data can be difficult. After the recording, you can modularize the test script by splitting it at appropriate steps and thereby creating meaningful chunks of test scripts. For example, for the test scenario in this tutorial, you can split the ‘Sign in’ and ‘Choosing the product’ steps and create two test scripts out of it. You can then add these scripts to a Compound Test to run in sequence.
    - Lesson 6: Abstracting data by using a dataset
      When you record a test, you perform a sequence of steps that you expect a user to perform. When you run this test, it uses the same data that you used during recording. However, in a real-life scenario, although a user might follow the same steps, the data that they enter into the application might be different at different point of time. To vary the data in the test, you use a data pool, which contains variable data. At run time, this variable data is substituted for the actual data in the recorded test.
    - Lesson 7: Associating the dataset with the test
      By default, at run time, the data pool values are accessed sequentially. You can specify whether the test uses the data pool values randomly or in a shuffled manner. If you have a long list of data pool values that are used by multiple tests from the same workspace, you can share a data pool.
    - Lesson 8: Running multiple test scripts in a sequence
      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.
    - Lesson 9: Adding a loop
      You will add a loop to the test so that the test is repeated to fetch all of the values from the data pool. Because your dataset has three entries, the test must run at least three times.
  - Tutorials for testing in the Functional Test perspective
    You can use the tutorials to get started with testing in the Functional Test perspective in Rational® Functional Tester.
- Samples
  This section describes about the sample project which can be used with HCL OneTest™ UI to test the functionality of an application.
- Administrator guide
  Typically, a user with the administrator role is responsible for certain tasks including installation, configuration, and integration of the product. This guide lists all such topics.
- 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.
- Test Execution Specialist guide
  A test executor automates the playback of the tests by using different methods such as Docker, IBM Cloud Private, Jenkins and so on. The test results can be pushed to HCL Quality Server.
- Test Manager guide
  As a test manager, you can keep track of the performance of the application by evaluating the test results. Following topics cover how you can work with the test results.
- Troubleshooting
  While working with HCL OneTest™ UI, you might encounter some problems that you can easily troubleshoot. The topics in this section address some of these problems.
- Reference
  Use these additional topics to gain more knowledge about the product.
- All Guides (PDF)
  You can find the link to view or download the content of the release notes, system requirements, and persona guides of IBM® Rational® Functional Tester as a PDF file.
- Security Considerations
  You can take certain actions to ensure that your installation is secure, customize your security settings, and set up user access controls.
- Notices
  This document provides information about copyright, trademarks, terms and conditions for the product documentation.

Lesson 5: Modularize the test script

In this tutorial, you recorded a test scenario in which you signed in to the web site, browsed for a product, and saw pricing details. In the actual scenario, you would have also recorded how to purchase, check out the product, and sign out of the website. You would have done that to avoid recording the same application multiple times. However, maintaining a big test script with a lot of data can be difficult. After the recording, you can modularize the test script by splitting it at appropriate steps and thereby creating meaningful chunks of test scripts. For example, for the test scenario in this tutorial, you can split the ‘Sign in’ and ‘Choosing the product’ steps and create two test scripts out of it. You can then add these scripts to a Compound Test to run in sequence.

Procedure

To modularize the test script:

Select the steps from ‘Click on Edit text … where you entered ‘rational test workbench’ in the Search field to Close browser window in the test script, both inclusive.
Right-click the selection and click Split Mobile or Web UI actions.
The Refactoring test window opens. On the right side of the Refactoring test window, under After Refactoring, examine the changes to be performed as a result of the split. Then, click Next. The selected steps are added to a newly created node called the In application.
You will now add the steps that are in the In application node to a new test script.
To create an empty test and copy these steps to it, proceed as follows:
- 1. Click File > New > New Test.
- In File name, type ibm-web-purchase and click Next.
- In Description, type Test script to purchase and click Next.
- Select the Mobile and Web UI Feature check box and click Finish.
- From the ibm-web test script, right-click the In application node and click Cut.
- In the ibm-web-addtocart test script, right-click the root node and click Paste.
- Click File > Save.

Results

You have now moved the Choosing the product test steps from ibm-web test script to ibm-web-purchase. Note that you cannot run the ibm-web-purchase test script independently. You can run it only as part of a compound test.

Now, you will create a dataset and add data that will be used by the test.