Home
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.
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.
HCL OneTest™ UI proxy SDK
Extend automated functional testing support for your application's user interface controls.
ProxyObject hierarchy
While developing new proxies by extending existing proxies for any domain, it is important to understand the existing proxies and the hierarchies, so that you extend the right proxy.
Java domain proxy hierarchy
There are three types of Java™ controls. The Abstract Window Toolkit (AWT), Swing or Java Foundation Class (JFC), and Standard Widget Toolkit (SWT), or Eclipse controls. HCL OneTest™ UI supports testing all three types of controls under Java UI frameworks. For the complete list of Java controls that are mapped to individual proxies, see the rational_ft.rftcust file in C:\Program Files\HCL\HCLOneTest\FunctionalTester\bin. This file can help you understand of what proxy to inherit to create a new proxy for a control under the Java domain.

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.
- Tests in the UI Test perspective
  When you develop web applications, Windows-based applications, or mobile applications, you can use HCL OneTest™ UI to create functional tests for these applications. You must first record the tests and then use HCL OneTest UI to run the tests before you can view the test results.
- Tests in the Functional Test perspective
  When you develop Java, HTML, or Terminal-based applications, you can use HCL OneTest™ UI to create traditional functional tests for these applications. You must first record the tests and then use HCL OneTest UI to run the tests before you can view the test results.
- Extending the UI Test perspective with custom Java™ 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.
  - HCL OneTest™ UI proxy SDK
    Extend automated functional testing support for your application's user interface controls.
    - Introduction to proxy SDK
      With HCL OneTest™ UI proxy software development kit (SDK) you can extend automated functional testing support for your application's user interface controls (GUI test objects), beyond what is provided by HCL OneTest UI by default. The proxy SDK provides detailed documentation, API references and ready-to-use samples and tutorials on how to extend HCL OneTest UI to add support for testing new controls. It also helps you to extend already supported controls from the existing domains. You can develop proxies manually or by using the proxy wizards driven approach.
    - HCL OneTest™ UI architecture
      HCL OneTest™ UI can be extended to perform additional functions for which it needs to communicate with the application under test (AUT). To do that HCL OneTest UI first establishes a communication channel to the AUT which is called enablement.
    - Proxy development
      A challenge in functional testing is the variety of user interface (UI) frameworks that are available (for example, Java™ and HTML) and controls (for example, button and table) that testing must support. UI frameworks differ in architecture and programming models and the controls differ in their inheritance hierarchy, methods, properties data, and user actions.
    - TestObjects
      TestObjects are the script-side interfaces for proxies and application under test (AUT) controls. A TestObject is a connection point between the test script and a ProxyObject that connects to the real object in the AUT. During recording, statements are recorded and objects are added to the Object Map. The script uses the information from the Object Map to construct and find TestObjects.
    - ProxyObject hierarchy
      While developing new proxies by extending existing proxies for any domain, it is important to understand the existing proxies and the hierarchies, so that you extend the right proxy.
      - Java domain proxy hierarchy
        There are three types of Java™ controls. The Abstract Window Toolkit (AWT), Swing or Java Foundation Class (JFC), and Standard Widget Toolkit (SWT), or Eclipse controls. HCL OneTest™ UI supports testing all three types of controls under Java UI frameworks. For the complete list of Java controls that are mapped to individual proxies, see the rational_ft.rftcust file in C:\Program Files\HCL\HCLOneTest\FunctionalTester\bin. This file can help you understand of what proxy to inherit to create a new proxy for a control under the Java domain.
      - .Net domain proxy hierarchy
        There are four key base proxies that you can extend to create new proxies for a control in the .Net domain. They are ObjectProxy, ComponentProxy, ControlProxy, and ControlWithSubobjectsProxy.
    - TestObject class diagram and canonical names
      HCL OneTest™ UI has a predefined set of TestObjects that are hierarchically grouped and each TestObject has a set of predefined methods.
    - SubItems
      SubItems are part of TestObjects. The ObjectMap does not contain the SubItems, because they are not mapped.
    - Value classes and value managers
      The following code examples show several value classes and value managers.
    - TestData types
      The HCL OneTest™ UI framework calls the getTestDataTypes() and getTestData(String) proxy methods for extracting data from controls for verification and reference. These methods are used during the creation and play back of data verification points. You can override the getTestDataTypes() method to add more specific data types for a control.
    - Proxy exceptions
      HCL OneTest™ UI has a set of predefined exceptions that covers wide ranges of errors that are usually expected while functional testing. These exceptions are available for both the Java™ and .NET proxy development frameworks.
    - Proxy development best practices
      Following best practices while you develop proxies can help make your work more efficient and effective. Consider these methods to enhance your development efforts.
  - Customizing a script template
    HCL OneTest™ UI uses its default script templates to format and provide basic information when you create a script. You can customize the information and format by customizing the script templates.
  - Using the API to edit functional test scripts
    These topics describe how you can take advantage of the HCL OneTest™ UI application programming interface (API) or the scripting framework to make changes to functional test scripts. As a general rule, the modifications that you make with the scripting SDK, should emulate as closely as possible, the user interactions to test with the application-under-test.
- Extending the functionality in the Visual Studio IDE
  These topics describe various ways that you can customize HCL OneTest™ UI or use the application programming interface (API) to extend HCL OneTest UI functionality.
- 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.

Java domain proxy hierarchy

There are three types of Java™ controls. The Abstract Window Toolkit (AWT), Swing or Java Foundation Class (JFC), and Standard Widget Toolkit (SWT), or Eclipse controls. HCL OneTest™ UI supports testing all three types of controls under Java UI frameworks. For the complete list of Java controls that are mapped to individual proxies, see the rational_ft.rftcust file in C:\Program Files\HCL\HCLOneTest\FunctionalTester\bin. This file can help you understand of what proxy to inherit to create a new proxy for a control under the Java domain.

You can extend these key base proxies for the Java domain:

JavaProxy
JavaGuiProxy
ComponentProxy and JComponentProxy
JfcGraphicalSubItemProxy and ScrollableSwtGraphicalSubItemProxy

JavaProxy: The JavaProxy proxy is the base proxy for all Java domain proxies. Fundamental Java object operation methods such as getProperties() and getMethods() are all implemented in this proxy.
JavaGuiProxy: The JavaGuiProxy proxy is the base proxy for all Java user interface (UI) elements. This proxy implements the IGraphical interface, which has methods for performing UI actions, such as click, double-click, drag, and recording methods.
ComponentProxy and JComponentProxy: The ComponetProxy proxy is implemented for AWT components and JComponentProxy for JFC at the same level of the hierarchy. Methods such as getChilderen(), getParent(), getOwner(), getOwnedObjects(), and getMethods() are implemented in these proxies specific to the components.
JfcGraphicalSubItemProxy and ScrollableSwtGraphicalSubItemProxy: The JfcGraphicalSubItemProxy proxy is implemented for JFC and ScrollableSwtGraphicalSubItemProxy for SWT at the same level of the hierarchy. They provide recording and playback of methods with SubItems. When a control contains different parts then the proxy for that control can be inherited from this proxy.

Proxy hierarchy for AWT controls

The following figure is a class diagram of the proxy hierarchy for AWT controls: AWT controls proxy hierarchy

AWT controls proxy hierarchy

Proxy hierarchy for Swing or JFC controls

The following figure is a class diagram of the proxy hierarchy for Swing or JFC controls: Swing or JFC controls proxy hierarchy

Swing or JFC controls proxy hierarchy

Proxy hierarchy for SWT controls

The following figure is a class diagram of the proxy hierarchy for SWT controls: SWT controls proxy hierarchy

SWT controls proxy hierarchy