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 LoadRunner Enterprise Administration, select Maintenance > Runs. The Runs Page is displayed.
To edit runs, under the Name column, click a run. By default, the Main Details view is displayed.
This page enables you to view and manage individual test runs across all projects in the system.
Filter. Filter the items you want displayed in the module, grid, or page. For details, see Filter.
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 panel.
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.
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.|
The name given to the test when it was created. Click the Runs link to display the run details in the Main Details view.
Note: You can edit the run name in the Main Details view.
The test's run ID.
The Controller involved in the test run.
The load generators involved in the test run.
The time, in minutes, that the test took to run.
Note: You can edit the duration in the Main Details view.
The start time of the run.
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.|
The test's domain name.
The test's project name.
The state of the test run. If a test is stuck in a particular state, you can change it.
The name of the user running the test.
Note: You can edit the tester name in the Main Details view.
|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.|
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:
The name given to the test when it was created.
Note: You can edit details in this field.
|Project ID||The test's project ID.|
|Test Name||The name given to the test when it was created.|
|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.|
The number of VUDs used in the test run.
The amount of VUDs involved in the action.
To list the events that occurred during the selected test run:
In LoadRunner Enterprise Administration, select Maintenance > Runs.
Under the Name column, click a run name.
Click the Event Logs tab.
The logs contain the following information:
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;
The module where the event originated.
The sub module where the event occurred.