Home
Test Manager Guide
This guide describes how to keep track of the performance of the application by evaluating the test results. This guide is intended for test managers.
Reports and counters
See the description of the counters for all of the performance reports.
Web service performance test reports
When you test a web service, these reports are produced during a run and saved after a run.
WSDL Coverage report
The Web Services Description Language (WSDL) Coverage report displays all the bindings, methods, and ports of a web service that were used in the test, compound test, or schedule. In this report, you can see the methods or ports that are not called by the test so that they require more tests for better coverage.

Test Manager Guide
This guide describes how to keep track of the performance of the application by evaluating the test results. This guide is intended for test managers.
- Evaluating results in web analytic reports
  After the test run, evaluate the results in the web analytic reports. Web analytics collect data using new technologies thereby providing better user experience.
- Logs overview
  HCL OneTest™ Performance uses logs to store different types of information, which you can use to determine the reason for a test failure.
- Reports and counters
  See the description of the counters for all of the performance reports.
  - Requirements report
    From version 9.2.0.1, the Performance Requirements report is renamed to Requirements report. The Requirements report validates the performance and functional requirements that you set in a test or in a schedule.
  - Synchronization Point report
    This report provides information about the synchronization points in test runs and lets you manually release a user from a synchronization point. To release a user, right-click in the report and select Manage Synchronization Points.
  - Loops report
    This report summarizes the functionality of loops in a test.
  - Agents Health Report
    With the Agents Health Report, you can view the usage data of CPU, Memory, Threads, and JVM Heap for the agent machines involved in the run. The report shows usage data for the Agent Host and Agent Process on the agent machines. By default, the Enable Agent Health Report check box at Window > Preferences > Test > Test Execution is selected. Also, by default, the report opens in the Compare mode. You cannot disable the compare mode.
  - Rate Runner report
    You can use the Rate Runner report to view how all the Rate Runner groups in the Rate Schedule have performed during the run.
  - Transaction report
    This report summarizes the success of transactions in the run, plots on a graph the response trend of each transaction during a specific sample interval, and shows the transaction throughput.
  - Transaction Percentile report
    This report shows the 85th, 90th, and 95th percentile elapsed times for all users, the union of all transactions in a run, and for the 10 slowest transactions in a run.
  - Transaction Net Server Time Percentile report
    This report shows the 85th, 90th, and 95th percentile net server times for all users and the union of all transactions in a run. The report also shows the 10 slowest transactions in a run. The net server time corresponds to the cumulative server response times within a transaction. Net server time does not include think times and delays, which are included in the elapsed time.
  - Rate Generator report
    Use this report to determine if the transactions run at the rate that you specify.
  - HTTP performance test reports
    When you test an HTTP system, reports are produced during a run and saved after a run. You can then analyze the reports to know the performance of the system under test.
  - SAP performance test reports
    When you test an SAP application, these performance test reports are produced during a run and saved after a run.
  - Citrix performance test reports
    When you test a Citrix XenApp application, these reports are produced during a run and saved after a run.
  - Web service performance test reports
    When you test a web service, these reports are produced during a run and saved after a run.
    - Service Performance report
      The Service Performance report summarizes the validity of the run, summarizes the data most significant to the run, shows the response trend of the slowest 10 service calls in the test, the server health depending on requests, and graphs the response trend of each service calls for a specified interval.
    - Web Service Verification Points report
      The web service verification points report shows the status of the verification points in your tests.
    - WSDL Coverage report
      The Web Services Description Language (WSDL) Coverage report displays all the bindings, methods, and ports of a web service that were used in the test, compound test, or schedule. In this report, you can see the methods or ports that are not called by the test so that they require more tests for better coverage.
  - Socket performance test reports
    When you test a socket application, these performance test reports are produced during a run and saved after a run.
  - HTTP counters
    HTTP counters, which are displayed in the Performance Test Runs view, enable you to customize your reports with dynamic information that is updated for each run.
  - SAP counters
    SAP generic counters, which are displayed in the Performance Test Runs view, enable you to customize your SAP reports with dynamic information that is updated for each run.
  - Citrix counters
    Citrix generic counters, which are displayed in the Performance Test Runs view, enable you to customize your Citrix reports with dynamic information that is updated for each run.
  - Service counters
    Service counters, which are displayed in the Test Runs view, enable you to customize your service test reports with dynamic information that is updated for each run.
  - Socket counters
    With socket generic counters, which are displayed in the Performance Test Runs view, you can customize your socket reports with dynamic information that is updated for each run.

WSDL Coverage report

The Web Services Description Language (WSDL) Coverage report displays all the bindings, methods, and ports of a web service that were used in the test, compound test, or schedule. In this report, you can see the methods or ports that are not called by the test so that they require more tests for better coverage.

To generate a WSDL Coverage report, in the Test Navigator view, right-click a service test result, and click WSDL Coverage Report.

Global Summary

This section displays the number of tests, verification points, and defects available in the report.

WSDL Coverage Summary

This section includes sub-sections for the name of all the compound tests, schedules, and test runs for each WSDL service. For example, if you run a compound test that contains four tests and each test runs a different WSDL service, this section displays a table with four rows for the same compound test but different WSDL services used. Another table displays each test run with the corresponding WSDL service. The tables would display a column for the overall coverage percentage of each WSDL service.

WSDL Coverage Details

This section also includes sub-sections for the names of all the compound tests, schedules, and test runs for each WSDL service. However, this section provides detail coverage information at the bindings, methods, and ports level for the WSDL service. It reports the verdict and the number of requests sent and responses received. The Coverage column of the table indicates whether the methods or ports are called by the test. If the method is called, it shows as 100%. If the method is not called, it shows as 0%. The percentages are then rolled up to the bindings and WSDL service level.

For example, in the following screenshot, there is one binding BasicHttpBinding_IStockQuoteService with two methods. The method GetStockQuote is called by the test. But, the GetWorldMajorIndices method was not called. Therefore, at the binding level, you see 50% coverage. As a user of the web service, if the GetWorldMajorIndices method is required, you can check why it was not used by the test. WSDL Details coverage

WSDL Details coverage