Run results

The Runs page provides test details, status, and run highlights for your load test.

Test run status

To access the Runs page, go to the Load tests tab, select a test, and click Runs Runs pane button in the sidebar. The Runs page displays a list of past runs with the status of the run.

The following table summarizes the possible values for the test status.

Status	Description
Aborted	You stopped the test during the initialization.
Failed	The test has ended and one or more SLAs were broken.
Halted	OpenText Core Performance Engineering stopped the test due to a security limitation.
Passed	The test has ended without any failed transactions.
Running	The test is currently running.
Stopped	You stopped the test and no SLAs were broken.
System Error	OpenText Core Performance Engineering was unable to run the test due to a server error.

Automatic archiving

The standard archiving for test run results is three months. Results older than three months are automatically archived, except for results that were set as a benchmark. To obtain archived results, submit a service request. Test run results that were restored from the archive, are available for an additional 12 months before they are archived again.

In addition, a single test is configured to manage up to a maximum 1000 test runs. When the maximum number of runs are exceeded, the oldest runs are archived for that test.

Test details and actions

The following table describes the data displayed for each test:

Item	Description
Status	The status of your test run. For details, see Test run status.
Start Time	The start date and time of the test.
Duration	How long the test ran.
Vusers	The numbers of Vusers allocated to the test.

The following table describes the actions that you can perform on your test results:

Action	Description
Set benchmark	Click the Benchmark button to set a run as a benchmark to compare with other runs on the dashboard.
View Dashboard	Click the Dashboard button to view the results in the dashboard. For details, see Dashboard.
Generate a report	In the Runs page, highlight a results row and click the Report button . For details, see Reports.
Export to a CSV	In the Runs page, highlight a results row, click the More options button , and choose CSV. For details, see Export as CSV.
Open a single user performance report	In the Runs page, highlight a results row, click the More options button , and choose Single user performance. For details, see Single user performance data.
Add a note	You can add a note to a completed test run, or to a running test after the initialization stage. To add a note, from the Runs tab click the More options button in a result row and from the menu displayed, select Add note. In the dialog box that opens, enter your note and save it. When a test run includes a note, the Note icon appears in the result row for the test. To edit an existing note, in the result row for the test run do one of the following: Click the More options button and from the menu displayed, select Edit note. Click the Note button . Note: You can add a note to a test run with any status, but its duration must be greater than zero.
Delete a run	In the Runs page, highlight a row (without clicking on its link), expand the More button and choose Delete run. Note: You can delete only test runs that have finished. If a test run has not finished, the delete option is unavailable. Deleted test runs are removed from the list and also from Results, but still appear in the License Usage report (marked as Deleted).

Result highlights

Above the list of tests, the following results highlights are displayed:

Graph name	Description	What does it tell me?
Last 5 runs	A graphical representation of the Run list grid. The graph provides a concise view of the last five runs of your load test.	Overview of the status of the last runs of your test. Quickly focus on failed runs.
Slowest transactions	Comparing the last two runs, the graph displays the top three transactions that slowed the test down the most.	Highlights which transactions in the application have performance regressions during test runs.
Top failing transactions	The graph displays the percentage of times that the top three transactions failed.	Highlights the transactions in the application that have experienced the most failures.

Next steps:

Results