Lesson 4: Play back the script

In this lesson, you will play back the script and look at some parts of the HCL OneTest UI interface. Because the script you just recorded is the active script, that script will play back when you click the playback button.

To start at the beginning of the tutorial, see the HCL OneTest UI Tutorial.

Because the script you just recorded is the active script, that script will play back when you click the playback button.

  1. To play back the script, click the Run Functional Test Script button Run Functional Test Script on the product toolbar, or click Script > Run.

  2. In the Select Log dialog box, keep the default log name of Classics and click Finish.

    The HCL OneTest UI window minimizes, and the Playback Monitor opens at the top right of your screen. As the script plays back, messages display in the Playback Monitor. HCL OneTest UI plays back all of your recorded actions, such as the application starting, the actions you performed on the application, and the verification points.

    When playback finishes, the HTML log displays the results of the run in a separate window. If the log is minimized, restore it. All events listed in the log should include Pass in the event headings in green. Notice that the two verification points you recorded are listed.

  3. Close the log window.

    Now that you have successfully recorded a script and played it back, let's look at the Functional Test perspective in more detail.

  4. If the HCL OneTest UI window is minimized, restore it.

When you have multiple scripts, HCL OneTest UI displays all open scripts in a project in the Editor (the script window). Each script has a tab in the banner of the window, and the tab for the active script shows the script name in bold. Any actions you perform on a script, such as playing it back, are performed on the active script.

Throughout the script, notice the information about the script shown at the top in light blue and prefixed by asterisks. This information comes from the script template, which you can modify. For more information, see Customizing a Script Template.

Notice also that HCL OneTest UI adds a short comment to the script in green characters to identify the object that the following lines refer to. This information makes it easier to navigate the script. Strings passed as arguments to methods during recording, including user inputs, are bright blue.

To the right of the Editor (the script window) is the Solution Explorer, which lists any Functional Test projects to which you are currently connected. All scripts within each project are listed below the project name. This Solution Explorer provides another way to navigate to a different script. When you double-click a script in the Solution Explorer, it opens in the script window and becomes the active script. For more information, see the Solution Explorer.

HCL OneTest UI main window

To the left of the Editor is the Script Explorer, which lists the verification points and object map of the active script. From the Script Explorer you can start the Verification Point Editor to display and edit verification points, and start the object map editor to display and edit object maps. For more information, see Script Explorer.

For information about the other parts of the HCL OneTest UI window, see About the Visual Studio .NET Window.

Advance to Lesson 5: View verification points and object maps.