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
After the tests or schedules are run and completed, you can view the results and open the reports to analyze the verdict, the performance, and statistics.
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.

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
  After the tests or schedules are run and completed, you can view the results and open the reports to analyze the verdict, the performance, and statistics.
  - Requirements report
    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.
  - 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.

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.

Report

CPU: The CPU usage graph shows the usage data for the Agent Host and Agent processes. Note that the SAP, SOA, and HCL OneTest™ API test extensions runs as external processes on the agent locations and therefore are not counted in the Agent process but are counted in the Agent Host with all others system processes (including the agent).
Memory: The Memory usage graph shows the memory consumed by the Agent processes in terms of average and percentage and by the Agent Host. The average memory consumption of the agent is usually very little. Therefore, the graph also displays the memory consumption in terms of percentage. If the CPU and Memory consumption for the agents is high, you can decide to add more locations to the execution of the performance tests.
JVM Heap: The JVM Heap graph shows the percentage of memory used compared to the total memory allocated and the total JVM memory allocated. If the memory used is high, you can decide to increase the JVM Heap size by adding the -Xmx property to the agent location.
Threads: Threads Usage graph shows the percentage of threads used for the currently running tasks compared to the maximum of threads that the tool can create. It also shows the number of tasks waiting for the threads to be made available to execute them.