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.
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.

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
  Rational® Performance Tester 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.
    - Performance report
      The performance report summarizes the validity of the run and the data that is most significant to the run. The report also shows the response trend of the slowest 10 pages in the test and the graph of the response trend of each page for a specified interval.
    - Page Element report
      This report summarizes the most important page element data for the run.
    - Why response time of a page does not equal the sum of its requests
      The response time for a page typically differs from the sum of its requests. This does not mean that your data is incorrect. The difference can be caused by concurrent requests, page connection times, inter-request delays, and custom code within a page.
    - Page Percentile report
      This report shows the 85th, 90th, and 95th percentile response times for all users and all pages in a run, as well as for the 10 slowest pages in a run.
    - Verification Points report
      This report shows the status of the verification points in your tests.
  - 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.

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.

In a performance report, you can sort the order of HTTP pages that are captured in a test or schedule either by alphabetical order or order of execution of the HTTP pages. The default sorting of the HTTP pages is by order of execution.