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.

This report plots the sample intervals within a run. You set the Statistics sample interval value in the schedule, as a schedule property.

Overall page

The Overall Transaction Rate graph shows the average elapsed time for all transactions during a specific sample interval. Elapsed time is the actual time spent within the transaction container. If you have staged loads in the schedule, this graph also delineates the stages with time range markers, in various colors, at the top.

The table under the graph lists the following information:

  • The average elapsed time for all transactions in the entire run.
  • The standard deviation of the elapsed time. The standard deviation tells you how tightly the data is grouped about the mean. For example, assume that System A and System B both have an average elapsed time of 12 ms. However, this does not mean that the elapsed times are similar. System A might have elapsed times of 11, 12, 13, and 12 ms. System B might have elapsed times of 1, 20, 25, and 2 ms. Although the mean time is the same, the standard deviation of System B is greater and the elapsed time is more varied.
  • The longest transaction in the entire run.
  • The shortest transaction in the entire run.
  • The average net server time for all transactions in the entire run.
  • The standard deviation of the net server time.
  • The longest net server time in the entire run.
  • The shortest net server time in the entire run.

Elapsed Time vs. Time

The Elapsed Time vs. Time graph shows the average response of each transaction during a specific sample interval. Each transaction is represented by a separate line. If you have staged loads in the schedule, this graph also delineates the stages with time range markers, in various colors, at the top.

The table under the graph lists the following information for each transaction:

  • The minimum elapsed time for the entire run.
  • The average elapsed time for the entire run. This is similar to the graph above, but the information in the table is the average for the entire run rather than the average per sample interval.
  • The standard deviation of the average response time. The standard deviation tells you how tightly the data is grouped about the mean. For example, System A and System B both have an average response time of 12 ms. However, this does not mean that the response times are similar. System A might have response times of 11, 12, 13, and 12 ms. System B might have response times of 1, 20, 25, and 2. Although the mean time is the same, the standard deviation of System B is greaterand the response time is more varied.
  • The maximum elapsed time for the entire run.
  • The rate, per second, at which the transaction was completed.
  • The number of attempts for the transaction.

Net End-to-End time vs. Time

Net end to end time for a transaction is a measured time of interactions with the server and a client such as a browser or a device. Typically, this does not include think times or processing time by the workbench.

Net Server Time vs. Time

Net server time for a transaction is a measured time of interactions with the server. Typically, this does not include think times or processing time by the product. The server interaction calculation is protocol specific. For example, in HTTP protocol, the net server time is exactly the sum of all page response times. The elapsed time (wall clock time) includes think time and other product processing overhead. For a Web UI test, the net server time includes the sum of time spent on the server and network.

Transaction Throughput

These line graphs provide an overview of the transaction frequency and the number of users that are adding load, both over the course of a run.
  • The Transaction Hit Rate graph shows the overall rates for starting and completing transactions during a specified sample interval. If you have staged loads in the schedule, this graph also delineates the stages with time range markers, in various colors, at the top. The summary table under the graph lists the transaction rate per second and the number of transactions that were completed for the entire run.
  • The User Load graph shows the number of active users and the number of users that completed testing over the course of the run. The summary table under the graph lists the number of active users, the number of users that completed testing, and the total number of users for the latest sample interval.

Transaction Health

The Transaction Health tab displays whether the transaction is healthy or unhealthy. When you define error conditions for a transaction, you can set whether the behavior of the errors affect the health of the run. If any one condition is met in a transaction, the transaction is marked unhealthy. The Transaction Health tab displays the percentage of healthy and unhealthy transactions. The graphic bar is displayed only if there are no errors.
Note:

During the test run, the elapsed time is recorded for unhealthy transactions. You can select the Discard time measurements for unhealthy transactions check box from the Test Execution Preferences (Windows > Preferences > Test > Test Execution), if you do not want to record the elapsed time for the unhealthy transactions.

Transaction Details

The Transaction Completion Percentage graph in the Transaction Details tab displays the overall percentage of the successful transactions. The Transaction Details section shows the transactions that were attempted, completed, exited, and the percentage of completed transactions.