Home
Tutorials
You can learn to start using HCL OneTest™ UI by reviewing the information in the Tutorials for the UI Test perspective and Functional Test perspective.
Tutorials for testing in the Functional Test perspective
You can use the tutorials to get started with testing in the Functional Test perspective in HCL OneTest™ UI.
Perform a data-driven functional test using Java scripts
In this tutorial, you will learn how to create a data-driven functional test using the HCL OneTest™ UI data-driven test wizard.
Lesson 6: Play back the test
In this lesson, you will play back the test you just recorded to see how easy it is to use a variety of data from a dataset to test the application.

Tutorials
You can learn to start using HCL OneTest™ UI by reviewing the information in the Tutorials for the UI Test perspective and Functional Test perspective.
- Tutorials for testing in the UI Test perspective
  You can use the tutorials to get started with testing in the UI Test perspective in HCL OneTest™ UI.
- Tutorials for testing in the Functional Test perspective
  You can use the tutorials to get started with testing in the Functional Test perspective in HCL OneTest™ UI.
  - Get started with functional testing using simplified scripts
    This tutorial introduces you to simplified test scripts and the application visuals and helps you get started with HCL OneTest™ UI for testing applications. It uses a sample Java™ application that is installed with the product for functional testing.
  - Create a functional test using Java scripts
    This HCL OneTest™ UI tutorial walks you through the major use cases for creating and playing back functional tests that use Java scripts. This comprehensive tutorial uses a sample Java™ application that is installed with the product.
  - Perform a data-driven functional test using Java scripts
    In this tutorial, you will learn how to create a data-driven functional test using the HCL OneTest™ UI data-driven test wizard.
    - Introduction: Perform a data-driven functional test using Java scripts
      In this tutorial, you will learn how to create a data-driven test using a variety of realistic data to test the application with the HCL OneTest™ UI data-driver wizard.
    - Lesson 1: Create a project and record a test script
      In this lesson, you will use the Classics CD sample application to create a new project and start recording a test to verify that the sample application correctly totals the amount of music CDs purchased.
    - Lesson 2: Data-drive a test
      In this lesson, you will use the data-driver to populate a dataset with data from the sample application. A dataset is a collection of related data records. A dataset supplies data values to the variables in a test script during test script playback.
    - Lesson 3: Add descriptive headings to the data
      In this lesson, you will add descriptive headings to the dataset you created in the previous lesson. Descriptive headings make it easier to add data to the dataset.
    - Lesson 4: Create a verification point with a dataset reference
      In this lesson, you create a verification point with a dataset reference to check that the price for the CD is correct in the ClassicsCD application.
    - Lesson 5: Add data to the dataset
      In this lesson, you will add data to the dataset to test the ClassicsCD sample application by placing more orders for the CD.
    - Lesson 6: Play back the test
      In this lesson, you will play back the test you just recorded to see how easy it is to use a variety of data from a dataset to test the application.
    - Summary: Create a data-driven test
      This tutorial has shown you how to create a data-driven test.
  - Test Adobe Flex application
    This tutorial walks you through the steps to enable your Adobe Flex application, and test the enabled Flex application from a local test computer using HCL OneTest™ UI. The steps are based on the roles that Flex developers and testers perform.
  - Test GEF applications
    The movies in this tutorial show you how to use HCL OneTest™ UI to test applications that are based on the Graphical Editing Framework (GEF). It also shows how HCL OneTest UI works with GEF objects.
  - Extend HCL OneTest™ UI capabilities using Proxy SDK
    The movies in this tutorial show you how to extend the HCL OneTest™ UI proxies using the proxy SDK.
- Tutorials for testing in the Visual Studio IDE
  HCL OneTest™ UI tutorials contain educational materials to help you learn the technologies and concepts behind products.

Lesson 6: Play back the test

In this lesson, you will play back the test you just recorded to see how easy it is to use a variety of data from a dataset to test the application.

About this task

Each time you play back a script with an associated dataset, the script accesses one record in the dataset. When you create a dataset reference for a verification point, the verification point uses the dataset reference to access a variable in that record. During playback, HCL OneTest™ UI substitutes the variable in the dataset for the dataset reference and compares the variable in the dataset to the actual results.

During playback you can view the script name, the script line number that is executing, status icons, and a description of the action in progress in the Playback Monitor.

Procedure

To play back the test script, click Script > Run.
In the Select log window, click Next.
Click the dataset Iteration Count arrow and then scroll to select Iterate Until Done to access all three records in the dataset.
Click Finish to use the default log name.

The HCL OneTest™ UI window minimizes, and the Playback Monitor is displayed in the upper-right area of your screen. Messages appear in the Playback Monitor as HCL OneTest™ UI plays back all of the recorded actions in the test script and enters data from the dataset.

When the test script finishes playing back, HCL OneTest™ UI displays a log with the test results. A log is a file that contains the record of events that occur while playing back a script. A log includes the results of all verification points executed that can be used to test the application.
Click X to close the log.