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.
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.
Preparing the functional test environment
This section describes the tasks you must perform to configure the functional test environment.
Flex applications testing process
The testing process is based on the tasks that Flex developers and testers perform. The process for automating functional tests of Flex applications differs, depending on the way developers create the application under test.
Test Flex applications that are not enabled using HCL OneTest™ UI
Developers can enable the RuntimeLoading component for Flex applications and provide the application on a web server for testing.
Deploying the Runtime loader components
You must deploy the Runtime loader components to test Flex applications that are not compiled using the HCL OneTest™ UI agent and Flex automation framework libraries.

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.
  - Preparing the functional test environment
    This section describes the tasks you must perform to configure the functional test environment.
    - Automatically enabled environment for functional testing
      From HCL OneTest™ UI version 9.1 onwards, HCL OneTest UI automatically enables the environments for functional testing.
    - Before you record
      Before you can start recording functional test scripts, perform the following setup and configuration tasks:
    - Enabling Java environments
      You need to enable Java™ environments before you can use HCL OneTest™ UI to test Java applications. HCL OneTest UI is shipped with a JRE that is automatically enabled during your installation. The JRE is called "Default JRE." To enable other JREs, or if you install a new JRE, you must run the enabler again.
    - Enabling web browsers
      To test the HTML applications in HCL OneTest™ UI, you must enable web browsers. You can then record and play back tests by using the browsers that you enabled.
    - Multiwindow support for functional HTML tests
      When you record functional test scripts for HTML applications, HCL OneTest™ UI provides multiwindow support to record actions that you perform on multiple windows of the same browser instance.
    - Preparing for functional testing in the Google Chrome browser
      You can use HCL OneTest™ UI to test HTML applications in the Google Chrome browser. To do this, you must enable the Google Chrome browser and add the HCL OneTest UI extension for Google Chrome™ to the browser.
    - Enabling the Eclipse non-p2 based applications for functional testing
      If the application under test is a non-p2 Eclipse based application, you can enable the Eclipse platform for functional testing using the Eclipse enabler.
    - Enabling the Eclipse p2- based applications for functional testing
      If the application-under-test is based on p2-based Eclipse, you must enable the Eclipse platform for testing using the Eclipse Software Updates feature.
    - Enabling stand-alone Standard Widget Toolkit applications
      You must enable stand-alone Standard Widget Toolkit (SWT) support before using HCL OneTest™ UI to test SWT applications in the application under test.
    - Configuring applications for testing
      You must configure your Java™, HTML, VB.NET, SAP GUI, Flex or Windows® applications for functional testing by providing the name, path, and other information that HCL OneTest™ UI uses to start and run the application. You use the Application Configuration Tool to configure applications.
    - Configuring the Java environment for testing
      You must configure JREs for testing Java only when the application under test is either Internet Explorer or a Java-based application that requires a Java distinct from the Java which is bundled with the product. The configured Java provides path, run options, and other information that HCL OneTest™ UI needs to access and use your JREs.
    - Configuring browsers for testing
      You need to configure your browsers for HTML testing with HCL OneTest™ UI. To configue browsers, you must provide name, path, and other information about the browsers.
    - Browser enablement diagnostic tool
      The Browser Enablement Diagnostic Tool is used to diagnose problems you might have with enabling your browser for HTML testing. The tool will diagnose the enablement problem and report how to solve the problem.
    - Enabling the Java plug-in of a browser
      The Oracle Java™ plug-in of your browser(s) must be enabled in order for some applets to be tested, and for the View Results link that launches the Verification Point Comparator from the HTML log to work properly. If you get an error regarding the plug-in during HTML testing, or when trying to launch the Comparator, use the following steps to fix the problem.
    - Adding references to external resources
      Functional test scripts or projects may refer to or use external resources like the DLLs in .Net IDE or JAR files in Eclipse IDE. To enable the scripts or projects to use these files, you must add references to these files in HCL OneTest™ UI.
    - Proxy settings for freeform DataWindow PowerBuilder controls
      In HCL OneTest™ UI, from version 8.2.1 onwards, new proxies are available for recording and playback on freeform DataWindow PowerBuilder controls in functional test scripts. By default, in a HCL OneTest UI 8.2.1 installation, scripts that you recorded using the old proxies can be played back normally but any new scripts that you record will use these new proxies.
    - Setting up the environment for testing AJAX-based web applications
      You can test AJAX-based applications in two different ways; by setting the Auto Trace option to true or by setting the Auto Trace option to false. If you set the Auto Trace option to false, you must use the HCL OneTest™ UI APIs for AJAX in the script by manually inserting them.
    - Enabling SAP client and server
      To use HCL OneTest™ UI to test SAP applications, you must enable the SAP client and SAP server.
    - Enabling applications with WebDynPro controls for functional testing
      When you playback functional test scripts to test HTML applications with WebDynPro controls, you may get object not found exception or a weak recognition warning even if the control exists.
    - Enabling the GEF application
      You must enable the GEF support before using HCL OneTest™ UI to test GEF objects on the application under test.
    - Enabling response time breakdown
      You can enable response time breakdown to see how much time is spent in each part of the application as the test runs. To collect response time breakdown, the data collection infrastructure must be installed and running on all computers that are used in the distributed application under test.
    - Flex applications testing process
      The testing process is based on the tasks that Flex developers and testers perform. The process for automating functional tests of Flex applications differs, depending on the way developers create the application under test.
      - Setting up the development environment for Flex applications
        The developer must set up the development environment before enabling the Flex application for testing with HCL OneTest™ UI.
      - Setting up the test environment for testing Flex applications
        A correct environment setup for testing Flex applications helps ensure reliable functional testing results. The test environment is typically set up by the testers on the test computer.
      - Testing HCL OneTest™ UI enabled Flex applications
        Developers can enable the Flex applications for testing by building the Flex application with HCL OneTest™ UI agent and Flex automation framework libraries. After compilation, the developer must create an HTML wrapper that embeds the enabled Flex application and provide the application on a web server or on a local test computer for testing.
      - Test Flex applications that are not enabled using HCL OneTest™ UI
        Developers can enable the RuntimeLoading component for Flex applications and provide the application on a web server for testing.
        Configuring the non-enabled Flex application
        You can configure the Flex applications that are not compiled using theHCL OneTest™ UI agent and Flex automation libraries.
        Deploying the Runtime loader components
        You must deploy the Runtime loader components to test Flex applications that are not compiled using the HCL OneTest™ UI agent and Flex automation framework libraries.
        Testing nonenabled Flex applications
        Testers can test a Flex application that is not enabled for functional testing and is deployed on a web server.
    - Importing and exporting configuration and customization files
      You can configure and customize files in the configuration and the customization directories. The configuration files contains information such as the application that must be configured for testing. However, the customization files contain information about the external jar files used in your project, customization of any recognition properties, and third-party proxy extensions. You can export these files and later deploy them using the export and import utility. The default location for the configuration and customization file is C:\ProgramData\HCL\OneTestUI. For example: If you want to use the same configuration and customization files on different computers, you can archive these files and later deploy them using this utility.
    - Setting preferences
      You use the Preferences dialog box to customize HCL OneTest™ UI in a number of different areas, such as settings for time options; colors for the Verification Point Editor, the Verification Point Comparator, and the Object Map Editor; highlight color for test objects; operating system; playback; delays; log; playback monitor; ScriptAssure(TM); recorder; recording monitor; and the workbench.
  - Functional test assets
    This section describes the different types of functional test assets that are available in HCL OneTest™ UI.
  - Functional test projects
    A functional test project stores application test assets such as scripts, object maps, verification point baseline files, and script templates. You must create a functional test project before you can record scripts.
  - Working with functional test scripts (Windows-only)
    This section describes the process of creating functional test scripts to test your applications.
  - Verification points
    Verification points verify whether an expected behavior occurred during a test playback, or they verify whether there is a change in the state of a control or an object. When you create a verification point, you capture information about a control or an object in the application to establish this information as a baseline for comparison during the playback.
  - Functional tests with external data
    You can use external data to data-drive functional tests. When you data-drive a test, the script uses variables for key application input fields and programs instead of literal values so that you can use external data as you data-drive the application you are testing.
  - Testing terminal-based applications
    Use the HCL OneTest™ UI Terminal-based Applications feature to create test scripts and automate your host-application test cases. You can test host attributes, host field attributes, and screen-flow through a host application. It uses terminal verification points and properties, as well as synchronization code to identify the readiness of terminal for user input.
- 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.
- 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.

Deploying the Runtime loader components

You must deploy the Runtime loader components to test Flex applications that are not compiled using the HCL OneTest™ UI agent and Flex automation framework libraries.

About this task

You can use the following file for configuring and testing Flex 4.5 applications:

RunTimeLoaderFlex45.swf and RuntimeLoadingTestFlex45.html

Note: Testers can also deploy the necessary files to a web server, provided that testers can access the server. Although developers might not be familiar with HCL OneTest™ UI, the developer needs the Runtime loader source file and the HCL OneTest™ UI agent to enable and deploy the Flex application. Testers need to provide these files to the developer.

To deploy the Runtime loader components and enable testing of applications that are not compiled using HCL OneTest™ UI agent and Flex automation framework libraries, perform the following steps:

Procedure

Deploy the RuntimeLoadingTest.html and RuntimeLoader.swf files from the functional tester installation directory\FunctionalTester\Flex directory to the web server.
Provide the URL of RuntimeLoadingTest.html page to the testers, for example, http://localhost/RuntimeLoadingTest.html?automationswfurl=applicationtotest.swf, where applicationtotest.swf is the name of the Flex application to be tested.