Home
Rational® Functional Tester
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 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.
Managing functional test projects
A functional test project stores application test assets such as scripts, object maps, verification point baseline files, and script templates. You must create a functional test project before you can record scripts.
Deleting a Functional Test project
There may be times that you want to delete a project that is no longer needed from the Functional Test Projects view. If you use ClearCase® for source control, you can delete a project only from your view, or from your view and from the ClearCase VOB.

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.
- 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.
  - 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 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.
    - Preparing the functional test environment
      This section describes the tasks you must perform to configure the functional test environment.
    - Managing functional test projects
      A functional test project stores application test assets such as scripts, object maps, verification point baseline files, and script templates. You must create a functional test project before you can record scripts.
      - Creating a test project
        A test project stores application test assets such as scripts, object maps, verification point baseline files, and script templates. You must create a test project before you can record scripts. You must create a new test project or connect to an existing test project before you record a new script.
      - Connecting to a Functional Test project
        If you have an existing Functional Test project or another member of your team has a project you need to use, you can use this option to connect to the project.
      - Disconnecting a Functional Test project
        If you no longer need to work on a Functional Test project, you can remove it from the Projects view.
      - Deleting a Functional Test project
        There may be times that you want to delete a project that is no longer needed from the Functional Test Projects view. If you use ClearCase® for source control, you can delete a project only from your view, or from your view and from the ClearCase VOB.
      - Projects view
        The Functional Test Projects view, which is the left pane of the Functional Test Perspective, lists test assets for each project.
      - Creating a new functional test folder
        You can use folders to organize items in the Functional Test Projects view.
      - Exporting functional test project items
        You can export project items such as scripts, test object maps, Java™ files or Visual Basic files, datasets and application visuals to another functional test project.
      - Importing functional test project items
        You can import project items such as scripts, test object maps, Java™ files or Visual Basic files, and datasets into a Functional Test project.
    - Working with functional test scripts (Windows-only)
      This section describes the process of creating functional test scripts to test your applications.
    - Working with verification points
      Verification points verify that a certain action has taken place, or verify the state of a control or an object. When you create a verification point, you are capturing information about a control or an object in the application to establish this as baseline information for comparison during playback.
    - Driving functional tests with external data
      This section describes techniques you can use to data-drive functional tests with external data.
    - Managing functional test assets
      You can integrate HCL OneTest™ UI with IBM® Rational® ClearCase® or Rational Team Concert™ and manage functional test assets using any of these source control management tools.
    - Testing terminal-based applications
      Use the HCL OneTest™ UI Terminal-based Applications feature to create test scripts and automate your host-application test cases. You can test host attributes, host field attributes, and screen-flow through a host application. It uses terminal verification points and properties, as well as synchronization code to identify the readiness of terminal for user input.
  - 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
    HCL OneTest™ UI 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.
- 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.

Deleting a Functional Test project

There may be times that you want to delete a project that is no longer needed from the Functional Test Projects view. If you use ClearCase® for source control, you can delete a project only from your view, or from your view and from the ClearCase® VOB.

Procedure

If your project is not in a ClearCase® view, in the Functional Test Projects view, right-click the project you want to delete.
In the pop-up menu, click Delete.
HCL OneTest™ UI displays a message asking you to confirm the deletion.
Take one of the following steps to delete a project:
- If you do not use ClearCase® for source control of your project, click Yes. Functional Test removes the project from memory and from the hard disk.
- If a project is in a ClearCase® snapshot view, to remove the project from ClearCase® and from your view, select the Remove selected items from ClearCase check box, and then click Yes. To remove a project from your view and leave it in the ClearCase® VOB, clear the Remove selected items from ClearCase check box, and then click Yes.
- If a project is in a ClearCase® dynamic view, to remove the project from your view and from the ClearCase® VOB click Yes. Deleting a project in a dynamic view always deletes the project from your view and from the ClearCase® VOB.
CAUTION: Deleting a project not under ClearCase® source control cannot be undone.
If you use ClearCase®, you can restore a project in a dynamic or snapshot view. ClearCase® uses the rmname command when you delete a project. For information see the ClearCase® Help.