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.
Rational® Functional Tester proxy SDK
Extend automated functional testing support for your application's user interface controls.
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.
Setting up proxy projects
ProxyObjects are deployed as either JAR files which are proxies written in Java™, or as Assembly DLLs which are proxies written in C#, along with customization file with the .rftcust extension.

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.
- Testing 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.
- Testing 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 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.
  - Rational® Functional Tester proxy SDK
    Extend automated functional testing support for your application's user interface controls.
    - Introduction to proxy SDK
      With Rational® Functional Tester 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 Rational Functional Tester by default. The proxy SDK provides detailed documentation, API references and ready-to-use samples and tutorials on how to extend Rational Functional Tester 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.
    - Rational® Functional Tester architecture
      Rational® Functional Tester can be extended to perform additional functions for which it needs to communicate with the application under test (AUT). To do that Rational Functional Tester 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.
      - Understanding proxies
        A proxy object implements the prescribed Rational® Functional Tester interface for a UI control in the application under test (AUT). When you enable your application for testing, the proxy classes are loaded into the application and become part of it. A proxy object wraps around the actual control (the native object) in your application, making it testable in Rational Functional Tester. It is a connection point between the TestObject and the real control (object) being tested at the AUT.
      - Proxy development environment
        Rational® Functional Tester proxies can be developed either in Java™ or C# programming languages based on the UI framework of the application under test (AUT).
      - Setting up proxy projects
        ProxyObjects are deployed as either JAR files which are proxies written in Java™, or as Assembly DLLs which are proxies written in C#, along with customization file with the .rftcust extension.
      - Current level of proxy support that Rational® Functional Tester provides
        To develop proxies for a control, you must understand the current level of support that Rational® Functional Tester provides for that control . Consider that you want to add testing support for the Java™ swing UI control, javax.swing.JFormattedTextField.
      - Extending proxies
        Rational® Functional Tester needs UI control-specific information to perform functional testing operations such as recording, playback, verification points, and data driving. It tries to map the closest proxy if it finds a new control for which it has no proxy.
      - Extending proxies for Flex custom controls
      - Developing proxies using the Proxy SDK wizard
        Rational® Functional Tester proxy SDK supports wizard driven development of proxies. Proxy development life cycle stages such as creating a proxy project, creating a proxy class, exporting the proxy packages and deploying these proxies is done using the proxy wizards.
    - 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.
    - TestObject class diagram and canonical names
      Rational® Functional Tester 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 Rational® Functional Tester 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
      Rational® Functional Tester 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
    Rational® Functional Tester 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 Rational® Functional Tester 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.
- Experimental Features
  Rational® Functional Tester 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.

Setting up proxy projects

ProxyObjects are deployed as either JAR files which are proxies written in Java™, or as Assembly DLLs which are proxies written in C#, along with customization file with the .rftcust extension.

Setting up a proxy project in Eclipse

You can use Eclipse 3.2 or later to develop proxies in Java. To create a new Eclipse Java project:

Procedure

Perform one of the following steps:
- From the Eclipse menu, click File > New > Project.
- From the Eclipse toolbar, click New, select Java Project, and then click Next.
Type the name of the new project in the Project name field and click Next.
In the Java Settings page:
1. Click the Create new source folder link, and specify src as the folder name so that all source files are kept under the src directory; then click Finish.
2. Click Libraries > Add Variable, and select RATIONAL_FT_LIB; then click OK.
Click Finish.

Setting up a proxy project in Visual Studio .Net

You must use Microsoft® Visual Studio .Net to develop proxies in C# for .Net, Win, Siebel, and SAP domains. To create a new Visual Studio .Net C# project:

Procedure

Create a new project in either of two ways:
- From the Visual Studio menu, click File > New Project.
- From the Visual Studio toolbar, click New Project.
Select Visual C# as the project type and Class Library as the template to use.
Specify the name of the new project and the project location in the Name and Location fields.
Click OK.
Right-click References in the solution explorer and select Add Reference.
Click Browse, and select the C:\Program Files\HCL\HCLOneTest\FunctionalTester\bin\rtxftnet.dll assembly as a reference to the project.

What to do next

After your project is created and set up, you can start creating your proxy files. You must add a new C# file for each new proxy and similarly for new TestObjects.