Home
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.
Functional testing proxy SDK technology samples
Functional testing proxy SDK samples are simple examples of proxy source code and applications under test (AUT).
JFormattedTextFieldProxy
This JFormattedTextFieldProxy sample explains how create a new proxy class add new control properties and control data. The sample works with the application-under-test (AUT) sample.
Testing the sample
This proxy sample explains how to extend a proxy to add more control properties and control data.

Rational® Functional Tester
- Release Notes
  This document contains information about what's new, installation instructions, known problems in and contact information of IBM Customer Support.
- System Requirements
  This document includes information about hardware and software requirements for 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.
  - Functional test project to test a Java application
    The sample functional test project is created using the first few lessons of the "Create a functional test" tutorial . You can look at the test assets while you do the tutorial or after you complete it.
  - A HCL OneTest™ UI project to test an HTML application
    This is a sample functional test project that contains various functional test scripts for testing an HTML application. In this sample project, the IBM® Rational® Team Concert™ web client is used as an application under test.
  - Functional testing proxy SDK technology samples
    Functional testing proxy SDK samples are simple examples of proxy source code and applications under test (AUT).
    - ButtonProxy
      The ButttonProxy sample has two HCL OneTest™ UI proxies. There is one button control each for the Abstract Window Toolkit (AWT) and the Java foundation class (JFC). The sample works with the application-under-test (AUT) sample.
    - JFormattedTextFieldProxy
      This JFormattedTextFieldProxy sample explains how create a new proxy class add new control properties and control data. The sample works with the application-under-test (AUT) sample.
      - Testing the sample
        This proxy sample explains how to extend a proxy to add more control properties and control data.
    - CheckBoxProxy
      This CheckBoxProxy sample explains how to create a new proxy class and new TestObjects and then map them to the javax.swing.JCheckBox control. The sample works with the application-under-test (AUT) sample.
    - Button OverrideProxy
      This ButtonOverrideProxy sample explains how you can extend the recording behavior of HCL OneTest™ UI, add more properties and set up a simple value manager and value class. This sample proxy is written for the java.awt.Button control. The sample works with the application-under-test sample (AUT).
    - JSpinnerProxy
      This JSpinnerProxy sample explains how to extend recording behavior of a control with SubItems, and support the playback for the extended recording behavior. The sample works with the application-under-test (AUT) sample.
    - TreeProxy
      This TreeProxy sample explains how to extend recording behavior of a control with SubItems, and support the playback for the extended recording behavior. The sample works with the application-under-test (AUT) sample. To view the samples, you must import the tree proxy, tree application and the tree custom control for which the proxy is being written into your workspace.
    - Flex control proxy
      This FlexCustomControl sample explains how to extend the recording behavior of a control with SubItems and support the playback for the extended recording behavior. The sample works with the application under test sample. To view the samples, import the flex proxy for which the proxy is being written into your workspace.
- Administrator Guide
  This guide describes how to install HCL OneTest™ UI software. After you install the software, you can perform administration tasks such as license configuration and integration with other products. This guide is intended for administrators.
- Test Author Guide
  This guide describes how to create test scripts and enhances them by applying different test elements such as dataset, variables, and verification points.
- Test Execution Specialist Guide
  This guide describes how to automate 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
  This guide describes how to 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
  This guide describes how to analyze and resolve some of the common problems that you might encounter while you work with HCL OneTest™ UI.
- Reference Guide
  This guide describes the additional topics to gain more knowledge about HCL OneTest™ UI.
- 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.

Testing the sample

This proxy sample explains how to extend a proxy to add more control properties and control data.

Test the application sample to view the default value of the text control

Open the JFormattedTextFieldApp.java file that is available in the imported JFormattedTextFieldApp project folder.
Open the Functional Test perspective.
Run the JFormattedTextFieldApp.java script. The sample application is displayed.
To test the text control, record a functional test script and record a data verification point and properties verification point on any of the control in the sample application.
Notice that there is no separate proxy for javax.swing.JFormattedTextFieldProxy. Properties that are specific to the JFormattedTextFieldProxy control, for example, format string and unformatted value are not available for the getProperties() method. These values are also unavailable for data verification points.
Run testObject.getProperty("unformattedValue"). This throws the error message, Properties not found.

Extended capabilities in the proxy code

Added more control properties

Along with the default control properties that are provided, more control properties are added by extending the java.util.Hashtable getProperties() and Object getProperty(String propertyName) proxy methods.

Added more control data

Along with the default control data types that are provided, more control data are added by extending the java.util.Hashtable getTestDataTypes() and ITestData getTestData(String testDataType) proxy methods.

Deploy the binary files

Open the Java perspective.
From the JFormattedTextFieldProxy project, copy the JFormattedTextFieldProxy.jar and the JFormattedTextFieldProxy.rftcust to the customization directory. The default location for the customization directory is C:\ProgramData\IBM\RFT\customizationC:\ProgramData\IBM\HFT\customization.

Verify the proxy deployment

Restart HCL OneTest™ UI
After you deploy the proxies, running testObject.getProperty("unformattedValue") returns a valid property.
Before you deploy the proxies, data verification on the javx.swt.JFormattedTextField control returns only two data types. After you deploy the proxies, an additional data type Unformatted Value is included. You can also verify that the additional data type is present by using the getTestDataTypes() and getTestData("value") APIs.