History

The History page lists the changes made to the load test.

Overview

The History pane lists the changes made to the load test, along with a timestamp and the user who made the changes. By viewing the history, you can determine who changed the test's settings, who deleted the test run, who triggered the test run, or who changed its ramp-up time.

The following changes are not included in the history:

  • Network emulations, script assignments for on-premises load generators, schedules, advanced scheduling, and cloud LG Vuser configuration settings.

  • Changes made outside of the load test. For example, script reloading, script editing, removing or deleting agents from the project, and runtime setting changes made in global mode.

To access the History page:

In the Load tests tab, select a test and click History in the sidebar.

Runtime settings history

The following protocols support runtime setting change history.

  • DevWeb

  • TruClient - Mobile Web

  • TruClient - Native Mobile

  • TruClient - Web

  • TruClient 2.0 - Web

  • Web - HTTP/HTML

Note:  

  • When a script is reloaded, all previous runtime setting history records are purged.

  • If a script is deleted, its runtime setting history data will no longer be available.

  • Only changes made in local mode are shown in the history. Changes made in global mode are not included. To view changes made in global mode, go to the Assets > Scripts page. For details, see View script details.

Test run history

The following applies to the test run history entries.

Entry Description
Triggered test run

This entry indicates who initiated the test run.

This includes clicking Run test in the UI, calling a public API, or initiating a run through a CI plugin such as Jenkins, GitHub Actions, or Azure DevOps.

  • For test runs triggered by Test scheduler, the recorded user is SYSTEM (scheduled).

  • For test runs triggered by CI plugins or public APIs, the recorded user is the authenticated user.
Stopped test run

This entry lists the test runs that were ended manually or through an API call.

Test runs that were stopped internally are not recorded in the history. These include internal events such as an SLA breach, stopping due to a predefined test duration, completion of the specified number of iterations, or a system error.
Deleted test run This entry lists the test runs that were deleted manually or through an API call.

See also