Functional test logs

After playback finishes, you can view results in the log. Results include any logged events, such as verification point failures, script exceptions, object recognition warnings, and any additional playback information.

You can view Functional Test logs by setting the logging preferences.

Types of logs

You can use three types of Functional Test logs that to view your playback results. These logs contain the same information in different formats:

  • Text -- Displays a log in ASCII format in the HCL OneTest™ UI script window.
  • HTML -- Displays a log in HTML format in your default browser.
  • TPTP -- Displays a log using TPTP in the Functional Test script window.
  • XML -- Displays a log in XML format in your default browser.

Location of logs

When you set the Functional Test Log Type preference to HTML or Text, HCL OneTest UI stores these logs in a log folder in the same location as the Functional Test project, but not in the Functional Test project. The name of the log folder is the project name with a suffix of _logs. For example, if your Functional Test project is CalendarApp, HCL OneTest UI stores its HTML or text logs in the CalendarApp_logs directory. You can open these logs from HCL OneTest UI in the Projects view. If you select HTML, your default browser opens the HTML log file. If you select Text, the text log file opens in the Functional Test script window.

In the Projects view, the HTML and text logs are listed within each project. Each script in the project has its own node in the logs directory. You can right-click the script log node to open, rename, delete, import, export, or view any logs or verification points it includes.

To set the product to open the HTML and XML logs in a web browser, use the following commands:
  • Internet Explorer -
    assoc.html=htmlfile
  • Mozilla Firefox -
    assoc.html=FirefoxHTML-308046B0AF4A39CB
  • Google Chrome -
    assoc .html=ChromeHTML

Managing logs

Use the Projects view to manage HTML or text logs. The logs appear underneath the project directory. Each script in the project has its own node under the logs directory. You can select a log and right-click Open Log, Final Screen Snapshot, Delete, or Rename. If your script has a verification point, you can select the log and open it in the Verification Point Editor by clicking Open VP, or open it in the Verification Point Comparator by clicking Open Comparator.

You can view the results of a verification point from the HTML log. At the end of each verification point entry in the HTML log is a View Results link. Click that link to open that verification point in the Verification Point Comparator. If the verification point failed, the baseline and actual files are shown side by side so that you can compare the data. If you get an error about the Java™ plug-in when trying to start the Comparator, verify that your plug-in is configured properly. For instructions, see Enabling the Java Plug-in of a Browser.

Feedback