Share this page

# Manage test runs

The Runs page displays information for all test runs across all projects in the system. It enables you to view detailed information relating to the run state of the test, the Vusers involved, as well as host and timeslot information.

In this topic:

## View and manage test runs

You can view and perform actions on test runs from the Administration area.

In Administration, select Maintenance > Runs to view the runs list and to perform actions on runs. For details, see the Runs Page.

To drill down on a run, click the link in the Run Name column to open the run details page. By default, the Main Details view is displayed.

You can perform actions on test runs from the Runs page and from the run details page.

Runs Page

This page enables you to view and manage test runs across all projects in the system.

UI Elements | Description
--- | ---
| Filter. Filter the items you want displayed in the module, grid, or page. For details, see Filter displayed items. Note: The start time for runs is always displayed in the filter and cannot be cleared. You can change the displayed period in the Filter pane.
| Export to Excel file. Enables exporting information from the Runs grid to an Excel file. Data from the grid is saved to an Excel file and downloaded to the Downloads folder of the client user.
| Select Columns. Enables you to determine which fields to display in the grid.
| Refresh. Refreshes the grid so that it displays the most up-to-date information.
| Delete run. Deletes the selected test runs together with their results from the project, the Admin Runs list, and all trend reports in which they appear. Note: Enabled when the selected test runs are in an inactive state only. Runs are deleted from the project's repository after 7 days. For details, see Deleting entities from a project.
| Stop Run. Stops the selected tests that are currently running. Note: Enabled when the selected test runs are in the Initializing, Running, or Stopping states only.
| Data Processor Queue. If you analyze a test run after it has run, or recalculate the SLA, or add the test run to a trend report, then the action is added to a data processing queue, enabling you to see when the action is performed.
Run Name | The name assigned to the run when it was created. Note: You can edit the run name in the Main Details view
Test Name | The name assigned to the test when it was created. Click the Runs link to display the run details in the Main Details view.
Run ID | The test's run ID.
Controller | The Controller involved in the test run.
Load Generators | The load generators involved in the test run.
Duration | The time, in minutes, that the test took to run.
Start Time | The start time of the run.
End Time | The end time of the run.
Load Test Unique ID | The identification number of the performance test. This number is automatically generated by the system when the performance test starts running.
Domain | The test's domain name.
Project Name | The test's project name.
State | The state of the test run. If a test is stuck in a state, you can change it.
Tester | The name of the user running the test.
Total in use Vusers | The number of Vusers that were initialized at least once during the run.
Timeslot ID | The ID of the test run timeslot.
Temp Results Directory Path | The path of the directory where the test results are temporarily stored.

Main Details view

Displays the details of the selected test run.

The following fields are displayed in this view in addition to those described in Runs Page above.

UI Elements | Description
--- | ---
Project ID | The test's project ID.
Involved Vusers | The number of Vusers that were initialized at least once during the run.
Max Vusers | The maximum number of concurrently running Vusers during the run.
Average Vusers | The average number of concurrently running Vusers during the run.
Consume VUFDs | The number of VUFDs used in the test run.
VUFDs Amount | The amount of VUFDs involved in the action.

Back to top

## View event logs

To list the events that occurred during the selected test run:

1. In Administration, select Maintenance > Runs.

2. Under the Run Name column, click a run name.

3. Click the Event Logs tab.

   The logs contain the following information.

   UI Elements | Description
   --- | ---
   ID | The event ID.
   Type | An indication of the event's severity. From most to least severe: error, warning, or info
   Project | The project in which the event occurred.
   Creation Date | The date and time the event was logged.
   Description | A description of the event.
   Responsible | The user, or automated system process responsible for the event.
   Action | The category of action where the event occurred. Example: Run Test
   Category | The event category.
   Name | The name of the event.
   Flow Context ID | A GUID that indicates a unique action which relates to several events. For example, running a test.
   Context | The specific entity where the event occurred. Example: RunID: 73; Timeslot 1835;
   Module | The module where the event originated.
   Sub Module | The sub module where the event occurred.

Back to top

https://admhelp.microfocus.com Enterprise Performance Engineering,LoadRunner Enterprise 8942
Tips to improve your search results...OpenText™ Enterprise Performance Engineering Help Center OpenText™ Enterprise Performance Engineering Help 26.1 All View Local Help Center View Online Help Center Version: