Home
Test Manager Guide
This guide describes how to keep track of the performance of the application by evaluating the test results. Following topics cover how you can work with the test results.
Results for tests in Functional Test perspective
In this section, you will learn how to analyze test results in the Functional Test perspective.
Log Extension
You can create customized HCL OneTest™ UI logs in addition to the standard log formats: text, HTML, Test and Performance Tools Platform (TPTP), and XML. You can use the customized logs to view your playback results.
Deploying the extended log file
You can deploy your customized log file by exporting the plug-in in a format suitable for deployment.

Test Manager Guide
This guide describes how to keep track of the performance of the application by evaluating the test results. Following topics cover how you can work with the test results.
- Publishing test result to HCL OneTest™ Server
  The test result indicate the quality of the application under test. There could be different stakeholders to the application who do not have the product installed but want to check the quality of application. You, as the user of the product, can publish the test result to HCL OneTest™ Server so that others can view it from the web browser.
- Publishing specific results to the server
  If you have a single test result or multiple test results that are not published to HCL OneTest™ Server, you can publish a single or all of them simultaneously.
- Unified reports
  Unified reports in HCL OneTest™ UI provide a detailed overview of the test results. Unified reports also provide an extensive user interface that you can use to analyze or apply filters on the test results.
- Results for tests in UI Test perspective
  In this section, you will learn how to analyze test results in the Web UI Test perspective.
- Results for tests in Functional Test perspective
  In this section, you will learn how to analyze test results in the Functional Test perspective.
  - Functional test logs
    After the playback is complete, you can view the results in the log. The results include any logged events such as verification point failures, script exceptions, object recognition warnings, and any additional playback information.
  - Logging page
    You use the Logging page to set log and comparator options, such as preventing the script launch wizard from displaying on playback, displaying the log viewer after playback, and displaying a message before overwriting an existing log. You also use this page to indicate the type of log generated.
  - Setting log preferences
    You can set your log preferences to view functional test logs.
  - Disabling enhanced log results
    Logged events such as verification point failures, script exceptions, object recognition warnings, and other additional playback information are displayed in the playback log results. From HCL OneTest™ UI version 8.2 and later, the results of the getProperty() command are also displayed in the log results. If you do not require the log event to be displayed in the playback log, you can disable the event in the log results.
  - Viewing logs in the Projects view
    You can open a log from the Projects view. In Projects view, the HTML, XML, and text logs are listed within each project. The log list is displayed below the project. The log has the same name as the project, with _logs appended, for example, projectname_logs.
  - Viewing Dojo logs
    Dojo logs are based on XML logs and display a graphical representation of the test results. You can use Dojo logs to select filters and view verification points, failed verdicts, warning verdicts, and the detailed information on each action that is recorded in the script. Dojo logs open in the default browser after script execution.
  - Renaming and deleting logs
    You can rename and delete logs from the Projects view.
  - Log Extension
    You can create customized HCL OneTest™ UI logs in addition to the standard log formats: text, HTML, Test and Performance Tools Platform (TPTP), and XML. You can use the customized logs to view your playback results.
    - Extending a log
      You can customize your log files by configuring the plug-ins to extend an extension point and writing a class that designs your log.
    - Deploying the extended log file
      You can deploy your customized log file by exporting the plug-in in a format suitable for deployment.
    - Example: Creating a text log
      The following example shows how to create a text-log output from an empty test script.

Deploying the extended log file

You can deploy your customized log file by exporting the plug-in in a format suitable for deployment.

Procedure

In the project folder in the left pane of the window, right-click plug-in.xml.
Click Export.
Select Deployable plug-ins and fragments in Plug-in Development folder.
Click Next.
Select the plug-in from the Available Plug-ins and Fragments list.
Set the destination directory to export the selected projects for deployment.
The default destination directory on Windows is C:\Program Files\HCL\hclonetest and on Linux is /opt/HCL/hclonetest.
If the Eclipse environment is extended during installation of HCL OneTest™ UI, the log plug-ins need to be exported to the extended Eclipse location.
Click Finish.
In the Save Resource dialog box, click Yes.