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.
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.
Driving functional tests with external data
This section describes techniques you can use to data-drive functional tests with external data.
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.

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.
  - Preparing the functional test environment
    This section describes the tasks you must perform to configure the functional test environment.
  - Managing 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.
  - Working with verification points
    Verification points verify that a certain action has taken place, or verify the state of a control or an object. When you create a verification point, you are capturing information about a control or an object in the application to establish this as baseline information for comparison during playback.
  - Driving functional tests with external data
    This section describes techniques you can use to data-drive functional tests with external data.
    - Data-driving tests overview
      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-driven 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.
    - 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.
  - Managing functional test assets
    You can integrate HCL OneTest™ UI with Rational® Team Concert™ and manage functional test assets using any of these source control management tools.
  - 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.
  - Troubleshooting issues
    You can find information about the issues or problems that you might encounter while you work in the Functional Test perspective of HCL OneTest™ UI. You can also find the details about the causes and resolutions that you can apply to fix the issues.
- 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.
- 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.

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.

Each time you play back a script with an associated dataset, the script accesses one record in the dataset. The verification point uses the dataset reference to access a variable in that record. At playback, Functional Test substitutes the variable in the dataset for the dataset reference and compares it to the actual results.

The log contains the record of events that occur while playing back a script and the results of all verification points executed. Actual test results (with the dataset reference resolved) that vary from the baseline results are defects or intentional changes in the application.

In the following diagram, the left box represents typical script assets:

(1) Script with an associated dataset

(2) dataset

(3) Object map

(4) Verification point baseline -- A baseline is the captured data maintained with a script. The verification point, in this example, has a dataset reference.

The right box represents the following:

(5) Test log that records the verification points that passed or failed

(6) Expected data, equal to the script's baseline data, with dataset references resolved to the values in the active record at the time the verification test was performed.

(7) Actual data is the data from the software-under-test at the time the verification point is performed.

Script assets and the Script Playback Log

When you run a script the following events take place:

(A) The verification point accesses the data in the dataset creating the expected result from the baseline and the active dataset record.

(B) The dataset reference resolves and supplies data to the verification point.

(C) The expected result is compared to the actual result.

(D) Expected and actual results are recorded in the log. Any deviation from the expected results are logged as a failure in the test log.