Home
Samples
You can find the sample project that you can use 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).
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.
Examples you can use
This proxy sample explains how to extend the recording behavior of a control with SubItems and support for the corresponding playback.

Samples
You can find the sample project that you can use with HCL OneTest™ UI to test the functionality of an application.
- Sample 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.
  - 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.
    - Examples you can use
      This proxy sample explains how to extend the recording behavior of a control with SubItems and support for the corresponding playback.
  - 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.

Examples you can use

This proxy sample explains how to extend the recording behavior of a control with SubItems and support for the corresponding playback.

Extended Capabilities: Recording controls with SubItems

This proxy sample extends the processSingleMouseEvent() proxy API to modify the recording behavior of a spin control. Although a spin control has two buttons and one text control as its children, from a testing perspective it must be treated as a single control with no children appearing in the TestObject Map. (In the TestObjectMap, the buttons and the text are treated as SubItems.) The processSingleMouseEvent() implementation sets methods with suitable SubItems, for example atButton("UP") or atButton("DOWN") as parameters for recording. Also note that although there are child objects for the spin control, you must make sure they are not listed as separate TestObjects. Therefore, the getChildAtPoint() and getChildren() APIs are extended to return null values. These child objects are treated as SubItems.

Playback Support

To support playback for each SubItem that is introduced during recording, HCL OneTest™ UI looks for the screen rectangle for each SubItem through the proxy. The SubItem rectangle can be provided by extending java.awt.Rectangle getScreenRectangle(Subitem subitem) proxy API.

Deploy the binaries

Copy the JSpinnerProxy.jar and JSpinnerProxy.rftcust files to the customization directory and restart HCL OneTest™ UI to test the sample application-under-test (AUT).

Verify the recording behavior

You can verify the recording behavior of the spin control:

Before you deploy the proxies, when you record results of the up and down buttons of JSpinner, the clicks are recorded as button.click(), where each up and down control is treated as a separate control.
After you deploy the proxies, clicking on the up button is recorded as spinner().click(atButton("UP")). Notice that the buttons are treated and recorded as SubItems and not as separate TestObjects.

Verify the playback behavior

Before you deploy the proxies, playing back user actions with SubItems, for example spinner().click(atButton("UP")) throws an exception, Point not found.
After you deploy the proxies, playing back user actions with SubItems work fine.