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.
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.
Exporting functional test project items
You can export project items such as scripts, test object maps, Java™ files or Visual Basic files, datasets and application visuals to another functional test project.

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.
  - 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.
    - Functional Test Projects view
      The Functional Test Projects view, which is the default pane on the left of the Functional Test perspective, lists test assets for each project.
    - Creating a test project
      A test project stores application test assets such as scripts, object maps, verification point baseline files, and script templates. You must create a test project before you can record scripts. You must create a new test project or connect to an existing test project before you record a new script.
    - Connecting to a functional test project
      If you have an existing functional test project or another member of your team has a project that you need to use, you can use this option to connect to the project.
    - Disconnecting a functional test project
      If you no longer need to work on a functional test project, you can remove it from the Functional Test Projects view.
    - Deleting a functional test project
      There may be times that you want to delete a project that is no longer needed from the Functional Test Projects view.
    - Creating a new functional test folder
      You can use folders to organize items in the Functional Test Projects view.
    - Exporting functional test project items
      You can export project items such as scripts, test object maps, Java™ files or Visual Basic files, datasets and application visuals to another functional test project.
    - Importing functional test project items
      You can import project items such as scripts, test object maps, Java™ files or Visual Basic files, and datasets into a Functional Test project.
  - 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.

Exporting functional test project items

You can export project items such as scripts, test object maps, Java™ files or Visual Basic files, datasets and application visuals to another functional test project.

Procedure

Select the project in the Project view and click File > Export from the product menu. In the Export wizard, select Functional Test > Functional Test Project Items and click Next.
In the Select Items to Export page, verify that the items you want to export are selected and those you do not want to export are cleared.
Notes:
- The project items can be from any project.
To export the application visuals, select Export Application Visuals.
In the Specify the export destination field, enter the name or browse for the data transfer file, which is the file to export with the selected project items. If the file does not exist, HCL OneTest™ UI creates it with a .rftjdtr extension.
Click Finish.
HCL OneTest™ UI compresses a copy of the files into a data transfer file with the name you specified and appends a .rftjdtr extension.
When you export a script, HCL OneTest™ UI includes any necessary files, such as shared test object maps, even though you did not select them.
To view items in the data transfer file, you can use any file compression program that supports the .zip format.