Analyze a test run
This section explains how to analyze a test run.
Sign into your tenant
To start analyzing test runs, first sign into your tenant.
-
Open your Web browser and enter the tenant URL sent to you by your SaaS operator.
The Sign in window opens.
-
Enter your username and password and click Sign in.
-
The Runs page opens by default.
To sign out, click the User account button in the banner and select Logout. You can also use the User account button
to change the color theme to either Light or Dark.
Runs list
When you sign in, the Runs page opens by default. The Runs page displays the Runs list which includes the run ID, test name, start time, date, duration, and run phase.
Phase | Description |
---|---|
Initializing | The test is currently in initialization mode. |
Running | The test is currently running. |
Halted | The test stopped to due a streaming limitation. |
Ended | The test ended in accordance with the planned scheduling configuration. |
You can perform the following actions in the Runs list.
Action | Details |
---|---|
Delete runs |
Select up to 10 runs to delete. To delete a run, make sure that it is not used in a trend report. If one or more of the runs is in use by a trend report, none of selected runs will be deleted |
Search | Use the search box to find a specific run. For example, enter the Run ID or test name. |
Select date | Use the date picker to select a date or range of dates for the runs. |
Group by ![]() |
Group the list items by test name. |
Upload |
Upload a run from a local host. To upload a run, see Upload test runs. |
Show only ended runs | Switch on to show only runs that have ended, or switch off to show all runs. |
Analyze run results |
To analyze the results of a run, in the Runs list, click the Run ID link or click the Run summary button |
View metrics
As part of the run summary, you can also view metrics for the run. For details, see View the dashboard.
View errors
To view a detailed list of all errors encountered during a selected run, click the Errors tab. For more details, see Investigate errors.
Next steps: