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 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.
Working with datasets
A dataset is a collection of related data records which supplies data values to the variables in a test script during test script playback.

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.
  - 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.
    - Data-driving functional tests
      To data-drive a test script, you need to select the controls or objects in the application-under-test using either the Object Finder Tool method or the Test Object Browser method.
    - Working with datasets
      A dataset is a collection of related data records which supplies data values to the variables in a test script during test script playback.
    - Creating a dataset
      A dataset is a collection of related data records which supplies realistic data values to the variables in a test script during test script playback. You can create data from scratch or import existing data into a new dataset from another dataset or a .csv file.
    - Importing to datasets
      You can import test data into a dataset using a comma-separated value (CSV) file that enables you to import large volumes of test data to a dataset rather than manually entering them.
    - Inserting data-driven commands into a script by using an application visual
      You can add data-driven commands to the script by using an application visual.
    - Associating a dataset with a group in a simplified script
      You can associate a dataset with a group in a simplified script. With this capability, you can create multiple datasets for a script and associate the datasets with the groups in a script.
    - Encrypting datasets
      To secure test data, you must encrypt datasets. You can encrypt one or more columns of a dataset using a password. You are prompted to enter your password when you run a test that utilizes dataset with encrypted variables.
    - Decrypting Datasets
      You must decrypt the dataset if you want to export a dataset into a .csv file. If you decrypt a dataset, it revokes the protection offered to the test data in it.
    - Editing datasets
      After you data-drive a test to create a dataset or create an empty dataset, you can edit the records and variables in the dataset.
    - Replacing literals with dataset references
      If you have an existing test script, you can replace literal values in the script with dataset references to add realistic data to the script. You can find and replace all literals, or just the number, string, or boolean literals with a dataset reference.
    - Dataset references and verification points
      When you create a verification point with a dataset reference, you can supply variable data to make your tests more realistic.
    - Changing the dataset record selection order
      The test dataset record selection order determines how a test script accesses records in the test script's associated dataset when you play back the test script.
    - Associating a dataset with a test script
      You can associate a test script with a dataset to use external data to drive the application instead of using a literal value.
    - Associating a test script with a dataset
      You can associate a test script with a dataset to use external data to drive the application instead of using a literal value.
    - Linking datasets to a functional test script
      You can link datasets to a functional test script to override the existing dataset that is associated with the script. To link a dataset, you must include the functional test script in a compound test in the UI Test perspective, and then map the required dataset by using Dataset Mapper.
    - Removing a dataset association
      You can remove dataset association with a test script.
    - Deleting a dataset
      You can delete a dataset if you no longer require it.
    - Replacing literals with dataset references in the Visual Studio IDE
      If you have an existing test script, you can replace literal values in the script with dataset references to add realistic data to the script. You can find and replace all literals, or selectively replace the number, string, or boolean literals with a dataset reference.
  - 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.

Working with datasets

A dataset is a collection of related data records which supplies data values to the variables in a test script during test script playback.

You can use datasets to supply realist data and to stress an application with a realistic amount of data.

Using HCL OneTest™ UI, you can create a data-driven test by selecting the controls or objects in an application-under-test to data-drive. HCL OneTest™ UI creates a dataset in which you can edit and add data. You can use a single test script repeatedly with varying input and response data.

You can use the dataset feature in the following ways:

To add realistic data to a test script.
To import data from a dataset or a .csv file created using a spreadsheet application.
To edit dataset values.
To change the dataset record selection order to determine how the test script accesses an associated dataset during playback.

While working with simplified test scripts, you can either create a data-driven test script during recording or you can insert data-driven commands into the simplified test script by using the application visuals. You can also create multiple datasets for a script and associate a dataset to a group in a simplified script.

Private and shared datasets

Every test script that you create has a private test dataset associated with it. The initial private test dataset is a placeholder and is empty until you data-drive a test script, or add new data to it.

You can create a shared dataset by creating a new dataset, or you can associate a dataset with several test scripts to share a dataset.