Former report

Each test run generates a report that provides statistics about the test run. This topic describes LoadRunner Cloud's former report. For the new report interface, see Report.

Where do I find it?

Navigate to the Load Tests tab, select a test, and click to open the Runs page.

or

Navigate to the Results page.
For a selected test run, click the vertical ellipsis (more options) and select Report.
Switch off the New Dashboard & Report toggle .

Note: If the New Dashboard and Report toggle is switched on, the new report is displayed. For details on the new report, see Report.

Set the time frame to display in the report

The time frame for which report results are displayed is shown above the report.

You can change the time range using one of these options:

Drag, stretch, or shrink the time slider.
Change the start and end time counters.

All metrics affected by the time selection are displayed in green.

Add notes

When viewing a report, you can add notes to the test run and can also add notes to individual report sections.

To add a note to the test run:

Click the Note icon under the list of the report sections on the left. In the dialog box that opens, enter your note and save it.

To add a note to a specific report section:

Click the Add notes icon at the bottom of the section. In the dialog box that opens, enter your note and save it.

After you have added notes to report sections, you can share the report, including the notes, with other people. For details, see Share report results below.

Share report results

For details on exporting report results in different formats and for sending report results by email, see Run results actions.

Add a custom snapshot of a dashboard widget to the report

Save a snapshot of a widget for a specific filter, split and time period and display it in the report for the run.

Add a snapshot from the Dashboard

Navigate to Results > Dashboard for a specific run.
Zoom to a specific time frame in the test run.
Configure what data is displayed in a widget.
Click in the widget header to save the snapshot.

Preview the snapshot in the report

Navigate to Results > Report for a specific run.
In the navigation pane, select Custom Snapshots.

Limitations

Add a maximum of 5 snapshots per report.
If your test has more than 1000 transactions, a large scale test, a snapshot cannot contain more than 200 data rows.
If your test has less than 1000 transactions, a snapshot cannot contain more than 600 data rows.

Configure a snapshot for the report

Action	How to
Rename a custom snapshot	Double-click the snapshot name. Edit the text.
Exclude a snapshot from the report	Deselect the custom snapshot in the navigation pane.
Edit the custom snapshot description	Double-click the custom snapshot description. Edit the text.
Remove a custom snapshot	Click the X in top right hand corner of a custom snapshot in the report viewer.

Learn about report results sections

The following table shows the various sections available in load test reports.

Section	Description	Example
Summary	The report summary provides an overview of the test run including duration, status, and important performance statistics such as average throughput. Note: For custom widgets, the average value may be different due to a difference in granularity and the number of data points.
Scripts	The scripts overview section lists all the scripts that were included in the test definition, and their configuration.
Mobile Devices	The mobile devices overview section lists all the devices and device details that were included in the test definition.
Scripts Distribution	The Scripts Distribution section displays how the test Vusers were distributed geographically during the test run.
Transactions	The Transactions section provides detailed statistics on each transaction in your test. The list of transactions can be sorted by any column. If you selected General Settings > Group Transactions when you configured the load test, measurements for the transaction groups are also displayed. Transactions section columns The following data is displayed for transactions: Transaction: The script and transaction name. % Breakers: The percentage of transactions that broke the SLA threshold at any given time in the test run. SLA Status: The status of the SLA. N/A. The transaction was not monitored. Pass. The SLA was not broken. Fail. The SLA was broken. Avg duration: The average time it took for a transaction to complete. Min: The minimum time it took for a transaction to complete. Max: The maximum time it took for a transaction to complete. Std. deviation: The standard deviation for transaction response time. Passed: The number of transactions that ended with status Passed. Failed: The number of transactions that ended with status Failed. X Percentile: The average of the X percentile of transaction response time. Note:X is defined in the Load Test > SLA pane for the test. SLA Threshold: The SLA defined in the Load Test > SLA pane for the transaction. Percentile trend: Compared to the last run, the percentage increase or decrease in the maximum transaction time, for defined percentile, of all transactions. Example: Run 1: 90th percentile is 5 seconds, 90th percentile trend is 0. Run 2: 90 percentile is 6 seconds, 90th percentile trend is -0.20. (20% increase).
Hits per second	The number of hits (HTTP requests) to the Web server per second.
Throughput	The amount of data received from the server every second.
Total Passed Transactions	The number of transactions that passed during the load test run.
Total Failed Transactions	The number of transactions that failed during the load test run.
Transaction response time [Average]	The average amount of time it took the defined percentile of transactions to complete.
Errors Summary	A list of errors encountered by Vusers during the load test run. Errors Summary columns The following data is displayed for errors: Script: The name of the script. Error ID: The ID number of the error. Error message: Message description. Error count: The number of errors that occurred during the run of the test.
On-premises Load Generator Scripts	The table lists which scripts run on which on-premises load generators.
On-premises Load Generator Script Errors	The table lists the top three errors for each script that occurred on on-premises load generators during the test run. Note: This section is only available for scripts run on on-premises load generators version 3.3 or later.
SLA Results	The SLA Result section provides detailed statistics for each SLA in your test. SLA Result columns The following data is displayed for SLAs: Script: The name of the script that contains the SLA. Transaction: The transaction name that contains the SLA. % Breakers: The percentage of transactions that broke the SLA threshold at any given time in the test run. SLA Status: The status of the SLA. N/A. SLA threshold was not defined for this transaction. Pass. The SLA was not broken. Fail. The SLA was broken. SLA Threshold: The SLA defined in the Load Test > SLA pane for the transaction. X Percentile: An average of the X Percentile transaction response time. Note: X is defined in the Load Test > SLA pane for the test.
Additional Vusers	This section provides details for each time there was a change in load during the running of a test. Additional Vusers columns The following data is displayed for additional Vusers: Time (GMT): The actual time that the Vusers were added. Test Time: The time during the test the Vusers were added. Script: The name of the script for which Vusers were added. Requested: The number of Vusers that were added to the test. Successfully Added: The number of Vusers that were successfully added to the running test.
Custom Snapshots	This section include all the custom snapshots added from the dashboard.
Monitors	This section provides an overview of statistics collected for each monitor, either server or application, during the test run. You can also include Windows on-premises load generators in the monitors displayed in this section. To enable this feature, open a support ticket. Monitors columns The following data is displayed for monitors: Metric: The name of the metric. AVG: The average value of the metric. Max: The maximum value of the value.
Pause Scheduling	The table lists the pause and resume schedule actions that occurred during the test run. For information about pausing a test, see Pause scheduling. Pause Scheduling columns The following data is displayed for pause scheduling: Status: The status of the schedule—progressing or paused. Start time: The start time of the status. Duration: The duration of the status. Triggered by: The user that triggered the status. Message: Any relevant message or additional information.

Notes and limitations

Reports support up to 5,000 transactions. If you have more than 5,000 transactions, you may encounter performance issues in the Reports UI or in the Export to PDF or Word functionality.