Testing: Test Runs
Overview
Use this page to review and manage historical test run results. A test run is a single execution, completed, failed, or still running, of a load profile: the configured mix of virtual users and workload scenario LoadGen drives against a system under test. Test Runs is the historical record of every execution, giving you an at-a-glance view of how each test performed.
Load profiles are configured on Testing: Load Profiles, and runs are produced manually from Testing: Run Test or automatically from Testing: Schedules. While a run executes you track it on Testing: Active Test; once it finishes, it lands here. From here you drill into a run's full metric breakdown on Analyse: Analysis, or pin a run as a profile's baseline so later runs are scored against it.
This page lets you filter runs by date range, load profile, and status; read summary cards for success rate and load reached; and open any run's errors, measurements, or PDF report. You can select multiple runs to compare or delete in bulk, and clean up old history you no longer need.
Key concepts
- Load Profile - A configured mix of virtual users and the workload scenario they run. Each test run executes one load profile. (related: Testing: Load Profiles)
- Baseline - A run pinned as the reference point for a load profile. Every later run of that profile is scored against it. (related: Testing: Load Profiles)
- Score - A value out of 10 showing how a run compares to its load profile's pinned baseline. It shows a dash when no baseline is pinned or available. (related: Analyse: Analysis)
- Cleanup - A bulk, age-based deletion of test run history: every run older than a chosen threshold is permanently removed.
When to use it
- Reviewing how a specific test run performed before sharing results with stakeholders.
- Comparing a new run of a load profile against its pinned baseline to check for regressions.
- Investigating a failed run's errors before retrying the test.
- Filtering a long history by date range, load profile, or status to locate a specific run.
- Selecting several runs to compare them side by side or delete them in bulk.
- Cleaning up old runs to keep test history manageable.
Before you begin
- At least one test run has completed or failed, started from Testing: Run Test or Testing: Schedules; otherwise the table has nothing to show.
- Your account has permission to view test history, granted on Operations: Permissions.
- If you plan to filter by profile, know the exact load profile name as defined on Testing: Load Profiles.
Common workflows
Find and review a specific test run
Persona: Load-test operator
- Set From, To, and optionally Load Profile or Status, to narrow the history.
- Expect: The filter fields show your chosen values; the table has not reloaded yet.
- Select Search.
- Expect: The table reloads to only the runs matching your filters, and "Showing X-Y of Z tests" updates to the smaller count.
- Select the run's row to open it.
- Expect: The Test Details panel opens for that run, showing Moments, Measurements, and Errors.
Verify: The Test Details panel shows the Score, Duration, and tabs for the exact run you were looking for, confirming you found the right result.
Pin a baseline and track score trend
Persona: Load-test operator
- Locate a completed run of the load profile named svc.lg.pintail and select its pin-baseline action.
- Expect: If the profile already has a pinned baseline, a confirmation asks whether to replace it; confirming pins the selected run as the new baseline.
- Wait for a later run of the same load profile to finish, then reopen Test Runs.
- Expect: That run's Score column now shows a numeric value, such as 9.5 /10, instead of a dash.
- Tick the checkboxes next to up to five runs of that profile and select Compare.
- Expect: Run Comparison opens showing the selected runs together.
Verify: The newly scored runs display a numeric Score referencing the pinned baseline, and Run Comparison lists exactly the runs you selected.
Clean up old test history
Persona: Admin or load-test operator
- Select Cleanup.
- Expect: The Cleanup Test History dialog opens, showing a Delete tests older than field, Cancel, and Delete Old Tests.
- Enter the retention threshold and select Delete Old Tests.
- Expect: Runs started before that threshold are removed, and the table and summary cards refresh without them.
Verify: No run with a Started date older than the threshold remains in the table, and "Showing X-Y of Z tests" reports a smaller total.
Steps
Step 1
Open Test Runs.
Expected result: The page loads showing the Success Rate, Failed Users, Total Users, and Duration summary cards, the From/To/Load Profile/Status filters, and a table reporting "Showing 1-6 of 6 tests".
This is the starting view for reviewing which test runs have completed and how they performed.
- From and To default to the last 30 days (24/09/2026 to 24/10/2026).
- Load Profile and Status default to All Profiles and All Statuses.
- Each summary card shows a small trend chart beneath the headline value, with no numeric change indicator.
Step 2
Select Refresh above the results table.
Expected result: The table reloads using the same filters, and the toolbar now shows Refresh and Cleanup together with a Select all checkbox and a selection column at the left of each row.
Refreshing pulls in the latest run data and exposes the bulk-selection controls you need before using Delete or Compare.
- Cleanup opens the Cleanup Test History dialog for age-based bulk deletion.
-
Select all ticks every run currently listed for bulk actions.
Field reference
| Field | Purpose | Format / Validation | Required | Default |
|---|---|---|---|---|
| From | Sets the earliest start date included in the table. Moving it earlier widens the history shown; moving it later excludes older runs. Works together with To to define the review window. | Date (dd/mm/yyyy) | No | 30 days before today |
| To | Sets the latest start date included in the table. Moving it forward includes more recent runs, up to and including today; combined with From it bounds the review window. | Date (dd/mm/yyyy) | No | today |
| Load Profile | Limits the table to runs of one load profile, the configured mix of virtual users and workload scenario defined on Testing: Load Profiles. Leave at All Profiles to compare across every profile at once. | Dropdown, single select | No | All Profiles |
| Status | Limits the table to runs in a particular state, such as Completed or Failed, so you can isolate failures or confirm recent successes without scanning every row. | Dropdown, single select | No | All Statuses |
| Select all | Selects every run in the current view at once so Delete or Compare can act on the whole set instead of individually ticked rows. | Checkbox | No | unchecked |
| Delete tests older than | Sets the age threshold used by Delete Old Tests. A shorter window removes more history and frees more storage; a longer window keeps more runs available for comparison and as baselines. | Number of days | Yes | - |
Column reference
| Column | What it shows | How to read it |
|---|---|---|
| (select) | Marks a run as part of the current bulk selection used by Delete and Compare. | An empty box means the run is not selected; a ticked box adds it to the current bulk selection. |
| Test | Identifies the run in the list. | Shows the name given to the run at start; older, unnamed runs fall back to the load profile name so the row still reads clearly. |
| Score | Shows how the run compares to its load profile's pinned baseline, out of 10. | A numeric value means a baseline is pinned and active; a dash means there is no baseline pinned for that profile, or the pinned baseline is no longer in the history. |
| Load Profile | Shows which load profile the run executed. | Matches this run back to its configuration on Testing: Load Profiles. |
| Type | Shows how the run was started. | Manual is the value captured here, for runs started directly from Testing: Run Test; a different value would indicate a different trigger for the run. |
| Started | Shows when the run began. | The relative age tells you at a glance whether a run is recent without parsing the full timestamp. |
| Duration | Shows how long the run took to complete. | Compare consecutive runs of the same profile to see whether duration is stable or drifting. |
| Users | Shows the number of virtual users the run simulated. | This is the concurrency the run attempted; check Successful and Failed for the outcome. |
| Successful | Shows how many users completed the run without error. | Read alongside Users: Successful equal to Users means every simulated user completed cleanly. |
| Failed | Shows how many users errored during the run. | Read alongside Successful: Failed plus Successful should equal Users for a finished run. |
| Status | Shows the run's current state. | Completed and Failed are the two states visible in this history; open the row for the reason behind a Failed run. |
| Success Rate (KPI card) | Shows the percentage of users across the filtered runs that succeeded. | A small chart beneath the value gives a quick visual trend; there is no numeric change indicator. A drop from your usual rate signals a regression to investigate in the rows below. |
| Failed Users (KPI card) | Shows the average number of failed users per run across the filtered set. | A rising average across runs of the same profile points to a developing problem rather than a one-off failure. |
| Total Users (KPI card) | Shows the highest concurrent user count reached by any run in the filtered set. | This is the maximum, not the average, so one large run can set this value for the whole filtered set. |
| Duration (KPI card) | Shows the average run duration across the filtered set. | Compare against any single run's Duration in the table to spot unusually fast or slow runs. |
Controls reference
Search
Applies the From, To, Load Profile, and Status filters and reloads the table.
When to use: After changing one or more filters, to narrow the history to the runs you want to review.
Side effects: Read-only: changes which runs are displayed, does not modify any test run.
Clear Filters
Resets From, To, Load Profile, and Status back to their defaults.
When to use: When you want to return to the full recent history after narrowing it down.
Side effects: Read-only.
Refresh
Reloads the table and summary cards using the currently applied filters.
When to use: When you expect a run in progress to have finished or changed status and want the latest data without resubmitting filters.
Side effects: Read-only.
Cleanup
Opens the Cleanup Test History dialog, where you set an age threshold and permanently delete older runs.
When to use: When test history is growing large and you want to remove runs you no longer need for comparison or audit.
Side effects: Opening the dialog is read-only; confirming inside it with Delete Old Tests permanently deletes matching runs.
Select all
Ticks the selection checkbox on every run in the current view.
When to use: Before Delete or Compare, when you want to act on all currently listed runs.
Side effects: Read-only; only changes selection, not data.
Delete (bulk)
Permanently deletes every selected run from the test history.
When to use: When you have ticked one or more runs, with no cap on how many, that you no longer need.
Side effects: Mutating and irreversible: the selected runs and their results are removed.
Compare
Opens Run Comparison showing the selected runs side by side.
When to use: When you have ticked up to five runs and want to compare their metrics directly.
Side effects: Read-only; if more than five runs are selected, it shows a message instead of opening.
Clear (selection)
Clears the current row selection.
When to use: To back out of a bulk Delete or Compare without acting.
Side effects: Read-only.
Pin baseline
Marks the selected run as the baseline for its load profile; every subsequent run of that profile is scored against it.
When to use: After a run you trust as representative of normal performance, so later runs get a meaningful Score.
Side effects: Mutating: if the profile already has a pinned baseline, you are asked to confirm replacing it; confirming changes which run future Score values are measured against.
Unpin baseline
Removes the pinned-baseline marker from a run.
When to use: When a previously pinned baseline is no longer representative and you plan to pin a different run instead.
Side effects: Mutating: later runs of that profile show a dash in Score until a new baseline is pinned.
View baseline
Opens the baseline run that a given run's Score was measured against.
When to use: When you want to confirm which run is currently acting as the baseline for a profile.
Side effects: Read-only navigation.
Generate PDF report
Opens a report dialog for the run and produces a PDF summary of its results.
When to use: When you need to share or archive a run's results outside the platform.
Side effects: Read-only on the page; generating the PDF produces a downloadable file and does not change the run.
View detailed results
Navigates to the detailed analysis page for that run.
When to use: When summary figures such as Score, Successful, and Failed are not enough and you need the full metric breakdown.
Side effects: Read-only navigation.
Open run details
Opens the Test Details panel for that run, with Moments, Measurements, and Errors tabs.
When to use: To inspect what happened during a specific run without leaving the Test Runs list.
Side effects: Read-only.
Detail tabs (Moments / Measurements / Errors)
Switches the Test Details panel between the run's recorded moments, its raw measurements, and its errors.
When to use: Use Errors first on a failed run to see what went wrong; use Measurements or Moments to inspect performance detail on a successful run.
Side effects: Read-only.
Why?
Opens an explanation of how the run's Score was calculated.
When to use: When a Score value looks unexpected and you want to understand what it measures against.
Side effects: Read-only.
Close
Dismisses the currently open dialog, such as Test Details, the report, or a delete confirmation, without making changes.
When to use: When you are done reviewing a run or decide not to proceed with a delete.
Side effects: Read-only.
Delete (row)
Opens a confirmation, then permanently deletes that single run from history.
When to use: When one specific run is no longer needed, rather than clearing a whole age range with Cleanup.
Side effects: Mutating and irreversible once confirmed.
Delete Old Tests
Permanently deletes every run older than the threshold entered in Delete tests older than.
When to use: Inside the Cleanup Test History dialog, once you have set the age threshold you want.
Side effects: Mutating and irreversible: removes all matching runs in one action.
Cancel
Closes the Cleanup Test History dialog without deleting anything.
When to use: When you opened Cleanup to check the option but decide not to delete history now.
Side effects: Read-only.
Verify the result
After selecting Search, the table shows only runs that match your From/To range, Load Profile, and Status choices, and the "Showing X-Y of Z tests" count reflects the narrower set. Each matching row lists its Score, Users, Successful, and Failed counts so you can judge the outcome without opening it. Selecting a row opens the Test Details panel for that run, showing Moments, Measurements, and Errors. If the table is empty, select Clear Filters to confirm matching runs exist at all, then reapply one filter at a time to find where the range went too narrow.
Troubleshooting
- Symptom: The table shows no rows after filtering. Fix: Select Clear Filters to confirm matching runs exist at all, then reapply From/To or Load Profile/Status one at a time.
- Symptom: The Score column shows a dash for every run of a profile. Fix: Pin a representative completed run as the profile's baseline; scores appear on later runs once a baseline is pinned.
- Symptom: Compare does not open after selecting several runs. Fix: Compare is limited to five runs; untick rows, or select Clear, until five or fewer remain selected.
- Symptom: The table shows a load error instead of results. Fix: Select Retry; if it persists, confirm with your administrator that your account has permission to view test history.
- Symptom: Delete Old Tests did not remove a run you expected. Fix: Check that the run's Started date is actually older than the value entered in Delete tests older than; newer runs are kept.
- Symptom: A run you deleted is needed again. Fix: Deletion from this page is permanent; use Delete Old Tests and the row Delete action only for runs you are certain you no longer need.
Related articles
- Prerequisite: Testing: Load Profiles - defines the load profile each run executes and where baselines are pinned
- Prerequisite: Testing: Run Test - starts the manual runs that appear in this history
- See also: Testing: Schedules - scheduled runs also land in this same history
- See also: Testing: Active Test - where you monitor a run while it is still in progress, before it appears here
- Next step: Analyse: Analysis - View detailed results opens a run's full metric breakdown here
- Prerequisite: Operations: Permissions - grants the permission needed to view test history