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).
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.
Testing the button proxy sample
This proxy sample explains how to write a simple proxy, map proxies to controls, deploy proxies, and verify how proxies work.

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.
    - Testing the button proxy sample
      This proxy sample explains how to write a simple proxy, map proxies to controls, deploy proxies, and verify how proxies work.
  - 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.
  - 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.
- Functional testing samples for the Visual Studio IDE
  HCL OneTest™ UI ships with some example code you can use in your own scripts. You can open these examples from within the sample project shipped with HCL OneTest UI. The sample project was created using the HCL OneTest UI tutorial. For reference, you can look at the script and other test assets while you do the tutorial, or after you complete the tutorial, if you want to compare the script and test assets to your files or actually play back the script.
- Functional testing proxy SDK samples for the Visual Studio IDE
  HCL OneTest™ UI ships with some example proxy code you can use to learn about proxy SDK. You can open these examples from within the sample projects shipped with HCL OneTest UI.

Testing the button proxy sample

This proxy sample explains how to write a simple proxy, map proxies to controls, deploy proxies, and verify how proxies work.

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

Open the AWTButtonApp.java and JButtonApp.java files that are available in the imported ButtonApp project folder.
Open the Functional Test perspective.
Run the AWTButtonApp.java script. The sample button application is displayed.
To test the button control, record a functional test script and click the button control of the sample application.
Open the test object map. Notice that the Proxy Class Name (#proxy) property under Administrative properties for java.awt.Button is .java.awt.ButtonProxy. This is the default value for this control.
Similarly run the JButtonApp.java script. The sample button application is displayed.
To test the button control, record a functional test script and click the button control of the sample application.
Open the test object map. Notice that the Proxy Class Name (#proxy) property under Administrative properties for javax.swing.JButton is .java.jfc.AbstractButtonProxy. This is the default value for this control.
Notice that the button click action is recorded as button.Click()

Deploy the binary files

Open the Java perspective.
From the ButtonProxy project, copy the ButtonProxy.jar and the ButtonProxy.rftcust to the customization directory. The default location for the customization directory is C:\ProgramData\HCL\HCLOneTest\customization.

Verify the proxy deployment

After deploying the proxy, you can now verify the value of the control.

Restart HCL OneTest™ UI
Open the ButtonApp application as mentioned in the earlier section.
Record a functional test script to test the buttons of the sample application.
Open the test object map. Notice that the Proxy Class Name (#proxy) property under Administrative properties for java.awt.Button and javax.swing.JButton are sdk.sample.awt.ExtendedButtonProxy and sdk.sample.swt.ExtendedJButtonProxy respectively. This proxy sample extends the proxy method public String getDescriptiveName() to change the TestObject descriptive names for the java.awt.Button and javx.swt.JButton controls.
Notice that after you deploy the proxies, the click actions on java.awt.Button and javax.swing.JButton controls are recorded as button_button.click() and jbutton_button().click() respectively as the proxy changes the descriptive name given to the TestObject for these two controls