Testing: Test Runs
Overview
Use this page to review and filter historical test runs. A test run is one completed or in-progress execution of a load test, tied to the Load Profile it used and the date it started. Instead of tracking down results from wherever a test was launched, Test Runs gives you a single, filterable history of every execution so you can confirm a test finished, check its outcome, and investigate it further.
A run only appears here after you start a test from Testing: Run Test, using a Load Profile defined on Testing: Load Profiles; while a test is still executing, you follow it on Testing: Active Test instead. From a run listed here, you can open its full breakdown on Analyse: Analysis, or clean up and prune history you no longer need.
On this page you narrow the list by date range, Load Profile, and Status, then open, compare, or delete individual runs, select several at once for bulk delete or side-by-side comparison, and remove old history in bulk through Cleanup.
Key concepts
- Test Run - A test run is one completed or in-progress execution of a load test, recorded with the Load Profile it used and when it started. (related: Testing: Run Test)
- Load Profile - A reusable definition of the load a test executes, selected when the test is started. (related: Testing: Load Profiles)
- LoadGen Score - A single number that summarizes a completed run's overall health, shown on each row and expanded on in the full analysis. (related: Analyse: Analysis)
- Run Comparison - A side-by-side view of up to five selected test runs, used to check how their results differ from each other.
When to use it
- After starting a test, to confirm it finished and check its result.
- To find a specific past run by narrowing the date range, Load Profile, or Status.
- To compare several runs side by side before deciding what changed between them.
- To open a run's full report or jump to its detailed analysis.
- To remove individual runs, or prune history older than a chosen age, with Cleanup.
Before you begin
- At least one test run exists; runs are created by starting a test from Testing: Run Test.
- The Load Profile you want to filter by is defined on Testing: Load Profiles.
- Your account has permission to view test history; without it the page reports you lack permission instead of listing runs.
Common workflows
Find and review a past test run
Persona: Load-test operator
- Set the From and To date fields to the range you want to search.
- Expect: The date fields update to reflect the chosen range.
- Choose a profile from Load Profile and a state from Status, then select Search.
- Expect: The list reloads to show only runs matching every filter you set; if none match, the page shows No Test Runs Found.
- Open a matching run to inspect it.
- Expect: A details drawer opens with Moments, Measurements, and Errors tabs for that run.
Verify: The details drawer shows data for the run you selected, scoped to the filters you applied.
Compare recent runs
Persona: Operator checking results across runs
- Tick the checkboxes for up to five runs you want to compare.
- Expect: Delete and Compare buttons appear above the list, each showing the count of selected runs.
- Select Compare.
- Expect: The Run Comparison view opens showing the selected runs side by side; selecting more than five shows a message instead of opening it.
Verify: The Run Comparison view lists all selected runs together so you can check their results against each other.
Clean up old test history
Persona: Admin managing run history
- Select Cleanup.
- Expect: The Cleanup Test History dialog opens with a Delete tests older than field.
- Enter the age threshold and select Delete Old Tests.
- Expect: Every run older than the threshold is permanently deleted and the dialog closes; the list refreshes to reflect the remaining runs.
Verify: Runs older than the threshold you entered no longer appear in the list, regardless of the current date filter.
Steps
Step 1
Open Test Runs.
Expected result: The page loads showing the From, To, Load Profile, and Status filters, a Credentials expiring banner for an API token nearing its expiry, and, since no runs match the default one-day date range, a No Test Runs Found placeholder with Clear Filters and Start New Test.
This is where you find and manage every past test execution.
- From and To default to a narrow one-day range.
- Load Profile and Status default to All Profiles and All Statuses.
-
Start New Test is offered directly from the empty state.
Step 2
Select Refresh.
Expected result: The list reloads from the server and the Credentials expiring banner clears; once the reload settles, the page will show the same No Test Runs Found state if no runs match your current filters.
Refreshing is how you pick up a run that finished after the page first loaded, without touching your filters.
-
Refresh does not change From, To, Load Profile, or Status.
Step 3
Select Search.
Expected result: The list reloads under the current From, To, Load Profile, and Status values; since no runs fall in the default date range, the page again shows No Test Runs Found and No tests match the current filters.
Search is how you commit a filter change so the list reflects exactly what you're looking for.
-
Search re-applies all four filter fields together.
Field reference
| Field | Purpose | Format / Validation | Required | Default |
|---|---|---|---|---|
| From | Sets the earliest start date included in the results list. Move it earlier to widen the history you're searching, or later to exclude older runs. | date (mm/dd/yyyy) | No | 07/09/2026 |
| To | Sets the latest start date included in the results list; pairs with From to bound the date range searched. | date (mm/dd/yyyy) | No | 07/10/2026 |
| Load Profile | Narrows the list to runs started from one Load Profile. Leave it at All Profiles to see runs from every profile. | dropdown | No | All Profiles |
| Status | Narrows the list to runs in one state. Leave it at All Statuses to see runs regardless of outcome. | dropdown | No | All Statuses |
| Delete tests older than | Sets the age threshold used by Cleanup: every run that started before this cutoff is permanently deleted once you confirm. A larger value keeps more history; a smaller value prunes more aggressively. | number (days) | Yes | - |
Column reference
| Column | What it shows | How to read it |
|---|---|---|
| Run | Identifies which run the row represents, so you can tell runs apart at a glance. | Shows the run's given name if it was named when started; older unnamed runs show the Load Profile they used instead of a raw identifier. |
| Score | Summarizes the run's overall health as a single number, so you can spot runs worth investigating without opening each one. | Fills in a short time after the run finishes. Select Why? beside it for a short explanation, or open Analyse: Analysis for the full breakdown. |
| Status | Shows the run's current state at a glance. | Matches the value you can filter on with the Status dropdown above; use it to tell which runs completed, are still running, or need attention. |
Controls reference
Search
Applies the current From, To, Load Profile, and Status values and reloads the list.
When to use: After you change any filter value, to commit the new filter combination.
Side effects: Read-only: filters which runs are displayed, nothing is changed or deleted.
Clear Filters
Resets From, To, Load Profile, and Status to their defaults and reloads the unfiltered list.
When to use: When you're not sure the current filters are excluding the runs you expect to see.
Side effects: Read-only: only changes what is displayed.
Refresh
Reloads the current result set from the server without changing the filters.
When to use: While a test may still be finishing, to pick up its result without reapplying filters.
Side effects: Read-only: re-fetches data, no filters or records change.
Start New Test
Navigates away from Test Runs to begin a new test.
When to use: When no existing run covers what you need and you want to launch a new one.
Side effects: Navigation only; the new test itself is configured and started on the page it opens.
Select rows (checkboxes)
Ticks one or more rows, or every row on the current page with select-all, to act on them together.
When to use: Before using the bulk Delete or Compare actions.
Side effects: Read-only: marks rows as selected, nothing is changed until you choose Delete or Compare. Select-all only selects rows on the current page, not every run matching your filters.
Delete (selected runs)
Permanently deletes every currently selected run, after you confirm in the Delete selected runs dialog.
When to use: To remove multiple unwanted runs at once, such as every failed run on the current page.
Side effects: Mutating: permanently removes the selected run records. There is no cap on how many runs you can select for delete.
Compare
Opens the Run Comparison view for the selected runs, showing their results side by side.
When to use: To check how several runs differ from each other, for example before and after a change.
Side effects: Read-only: nothing is changed or deleted. Limited to five runs; selecting more shows a message rather than opening the comparison.
Clear selection
Deselects every currently ticked row.
When to use: To start a fresh selection before choosing different runs to delete or compare.
Side effects: Read-only: only changes which rows are ticked.
Cleanup
Opens the Cleanup Test History dialog, where you set an age threshold and delete every run older than it.
When to use: To prune old history across your whole run history, not just the runs currently visible or selected.
Side effects: Opens a dialog only; nothing is deleted until you confirm with Delete Old Tests.
Delete Old Tests
Confirms the Cleanup action, permanently deleting every run older than the threshold you entered.
When to use: Once you've set Delete tests older than to the age you want to prune.
Side effects: Mutating: permanently deletes runs across your full history, regardless of the current date, profile, or status filters.
Cancel (Cleanup dialog)
Closes the Cleanup Test History dialog without deleting anything.
When to use: If you opened Cleanup by mistake or change your mind about the threshold.
Side effects: Read-only.
Open report (row action)
Opens a report dialog for that run, where you can generate a PDF.
When to use: To produce a shareable summary of one run's results.
Side effects: Read-only until you select Generate PDF report inside it.
Generate PDF report
Produces a PDF export of the open run's report.
When to use: When you need to share or archive a run's results outside LoadGen.
Side effects: Produces a file; does not change the run record itself.
View detailed results
Navigates to Analyse: Analysis for that run's execution.
When to use: When the score and summary on this page aren't enough and you need the full result breakdown.
Side effects: Navigation only.
Show details (row action)
Opens a details drawer for that run, with Moments, Measurements, and Errors tabs.
When to use: To inspect one run's timeline, measurements, or errors without leaving this page.
Side effects: Read-only.
Moments / Measurements / Errors (detail tabs)
Switches between views inside the open run's details drawer: Moments, Measurements, and Errors.
When to use: Moments for the run's timeline of notable events, Measurements for its recorded metrics, Errors for what went wrong on a failed or partially failed run.
Side effects: Read-only.
Why? (score explainer)
Opens a short explanation of how that row's Score was calculated.
When to use: When a run's Score looks unexpected and you want to understand what drove it before opening the full analysis.
Side effects: Read-only.
Delete (single run)
Deletes one run, after you confirm in the Delete Test dialog (Are you sure you want to delete this test?).
When to use: To remove a single unwanted or mistaken run.
Side effects: Mutating: permanently removes that run's record.
Retry
Reloads data after a failed fetch: the main list if Test Runs itself failed to load, or a run's extended details if those failed to load inside its details drawer.
When to use: After a load failure banner or message appears instead of the expected list or details.
Side effects: Read-only: re-fetches data, nothing is changed.
Close
Closes whichever dialog or details drawer is currently open (report, run details, or run comparison) without making changes.
When to use: When you're done reviewing a dialog or drawer and want to return to the list.
Side effects: Read-only.
Dismiss error banner
Closes the error banner shown after a single-run or bulk delete fails.
When to use: After reading the failure message, to clear it from the page.
Side effects: Read-only: only dismisses the message; it does not retry or undo anything.
Dismiss Credentials expiring banner
Closes the Credentials expiring notice.
When to use: After you've noted which credential is expiring, or once you've reissued it.
Side effects: Read-only: only dismisses the banner; it does not reissue the credential.
Verify the result
After you set your filters and select Search, the list reloads to show only the runs matching your From/To range, Load Profile, and Status, with each matching run available to open, compare, or delete. If nothing matches, the page shows No Test Runs Found with a Clear Filters option instead of a table. Check first that your From/To range actually covers when the run executed, since the filters default to a narrow one-day window that hides anything outside it.
Troubleshooting
- Symptom: The page shows No Test Runs Found even though you expect runs. Fix: Select Clear Filters to rule out the date range, Load Profile, or Status excluding them, then Search again.
- Symptom: A Credentials expiring banner appears referencing an API token. Fix: Reissue the token under Configuration → Credential Profiles before it expires, so tests that depend on it keep running.
- Symptom: The page reports you don't have permission to view test history. Fix: Ask your administrator to grant you access; the list stays empty until your account has the right permission.
- Symptom: A message says your session has expired instead of showing the list. Fix: Log in again; the page can't load test history without an active session.
- Symptom: Selecting Compare on a large selection shows a limit message instead of opening. Fix: Reduce your selection to five runs or fewer.
- Symptom: A delete or bulk delete fails and shows an error banner. Fix: Dismiss the banner, then try again; if it keeps failing, confirm the run wasn't already removed elsewhere.
Related articles
- Prerequisite: Testing: Run Test - Test runs shown here are created by starting a test from this page.
- Prerequisite: Testing: Load Profiles - Defines the profiles you can filter test runs by.
- See also: Testing: Active Test - Shows a test while it's still running, before it becomes a historical run here.
- Next step: Analyse: Analysis - Opens the full breakdown behind a run's LoadGen Score and detailed results.
- See also: Configuration: Credential Profiles - Where you reissue an API token flagged as expiring in the banner on this page.