Functional Testing: Run History
Overview
Use this page to filter and review Functional Testing run history. A run is a single execution of a package's project, producing its steps, screenshots, log, and reports. Packages run on a schedule, through the API, from LoadGen Studio, or directly from an engine, so runs accumulate quickly; this page narrows that history by package, project, state, verdict, engine, trigger, gold image, or creation period.
A run needs a package with at least one project that has already run or is scheduled, both set up on the Functional Testing: Packages and Functional Testing: Schedules pages; a run can also record the gold image it ran against: see Testing: Gold Images (sign-in required). Once you find a run here, you open it to inspect the steps it executed, its screenshots, its log, and its reports, detail the Functional Testing: Dashboard only summarizes.
This page lets you combine those filters, pick a creation-time window from quick chips or a custom range, open any matching run for its full detail, and, if your role allows it, select and delete ended runs you no longer need.
Key concepts
- Package - A package groups one or more Functional Testing projects that are run and tracked together. (related: Functional Testing: Packages)
- Run - A single execution of a package's project; each run produces its own steps, screenshots, log, and reports.
- Verdict - The pass or fail outcome of a completed run, separate from its State. An Error verdict on a completed run means it finished but missed a pass rule, not that the run itself failed to execute.
- Trigger - How a run was started: Manual, Schedule, Api, Studio (a LoadGen Studio upload), or Engine (started directly from an engine). (related: Functional Testing: Schedules)
When to use it
- You want to check whether a scheduled or manually started functional run completed and what its verdict was.
- You need to open a specific run's steps, screenshots, log, or reports to investigate a failure.
- You want to audit how a package has been running over a period, for example the last 7 or 30 days.
- You need to confirm which engine or trigger a run used.
- You want to delete old ended runs to free up history, if your role allows it.
Before you begin
- At least one Functional Testing package exists with a project that has already run or is scheduled, created on the Functional Testing: Packages page; otherwise the table shows No runs yet.
- Your account's role can view Functional Testing runs.
- To use Delete selected runs, your account needs the Functional Testing Admin role; Operator and Analyst roles can view runs but not delete them.
Common workflows
Find a run by package and time range
Persona: Load-test operator
- Open the Packagedropdown and select the package whose runs you want to review.
- Expect: The list filters to runs belonging to that package, and the dropdown shows its name instead of All packages.
- Select the 24hchip (or another lookback chip matching your investigation window).
- Expect: All time stops being highlighted, 24h becomes the active chip, and the table reloads with only runs created in the last 24 hours.
- Select a State or Verdictvalue, for example to isolate runs that ended in error.
- Expect: The table reloads to show only runs matching the chosen state or verdict.
- Select a matching run row to open it.
- Expect: The run detail view opens, showing its steps, screenshots, log, and reports.
Verify: The opened run shows the package and project you filtered for, confirming you located the right run.
Remove ended runs you no longer need
Persona: Functional Testing admin
- Filter the list to the runs you want to remove, for example by Package and a Stateof Completed, Cancelled, or Error.
- Expect: Only matching ended runs remain in the table.
- Select the checkboxes next to the runs to delete.
- Expect: Delete selected runs becomes enabled.
- Select Delete selected runsand confirm.
- Expect: The selected runs, and their steps, screenshots, logs, and reports, are permanently removed from the list; a status message confirms the result.
Verify: The deleted runs no longer appear in the table under the same filters.
Steps
Step 1
Open the Run History page under Functional Testing.
Expected result: The page loads with every filter at its default, Package set to All packages, State, Verdict, and Trigger set to All, Engine set to All engines, Gold image set to Any gold image, and the Created period set to All time. Since no functional run has been recorded yet, the table shows a No runs yet empty state instead of a list of runs.
This is the starting view for locating and reviewing past Functional Testing runs.
- The Retention line reads 180 days for runs and screenshots 30 days, each counted from the run's creation date.
- Select Go to Packages or the Packages button to open a package and start a run, since none exist yet.
Field reference
| Field | Purpose | Format / Validation | Required | Default |
|---|---|---|---|---|
| Package | Narrows the list to runs belonging to one package; leave it at All packages to see runs across every package you can access. | dropdown | No | All packages |
| Project | Matches runs by the project's exact name; use it once you know precisely which project's runs you want without also picking its package. | text, exact name | No | - |
| State | Filters by the run's lifecycle stage. Use it to find runs waiting (Queued, Dispatched), currently executing (Running, Uploading), or finished (Completed, Cancelled, TimedOut, Interrupted, Error). | dropdown | No | All |
| Verdict | Filters completed runs by their pass or fail outcome, independent of State. Choose this when you want only runs that finished with a specific result. | dropdown | No | All |
| Engine | Narrows runs to the one execution engine that ran them; use it to check whether a specific engine, configured on the Functional Testing: Engines page, is producing failures. | dropdown | No | All engines |
| Trigger | Filters by how the run was started: Manual, Schedule, Api, Studio, or Engine. Use it to separate scheduled runs from ad-hoc ones when investigating. | dropdown | No | All |
| Gold image | Narrows the list to runs executed against one gold image. | dropdown | No | Any gold image |
| Image version | Narrows the list further to one version of the chosen gold image. | dropdown | No | Any version |
| Created (period) | Restricts the list to runs created within a time window. Choose a short chip like 1h or 4h to check a run you just started, a longer one like 7d or 30d to audit recent history, All time to remove the restriction, or Custom to pick exact dates. | chip selection or custom date range | No | All time |
Column reference
| Column | What it shows | How to read it |
|---|---|---|
| Select | A checkbox used to mark ended runs for bulk deletion. | Selecting one or more rows enables Delete selected runs; it has no effect on runs that are still in progress. |
| Package | Shows which package the run belongs to. | Useful to identify a row's source package when the Package filter is left at All packages. |
| Project | Shows the exact project name that was run. | Matches the name used in the Project filter. |
| State | Shows the run's current lifecycle stage. | Queued or Dispatched means the run is waiting, for example for an available engine; Running or Uploading means it is in progress; Completed, Cancelled, TimedOut, Interrupted, or Error means it has ended. |
| Verdict | Shows the completed run's pass or fail outcome as an icon plus a label, never colour alone. | An Error verdict on a completed run means it missed a pass rule, which is a different thing from the run failing to execute. |
| Engine | Shows which engine executed the run. | Matches the name used in the Engine filter. |
| Trigger | Shows how the run was started. | Manual and Schedule are the common cases; Studio marks a LoadGen Studio upload and Engine marks a run started directly from an engine. |
| Gold image | Shows the gold image and version the run was executed against, when one was used. | Blank for runs not tied to a gold image. |
| Version | Shows the package version the run used. | An amber chip marks a run made from saved changes that were never published; a dash marks a run from before this platform tracked versions. |
| Checks | Shows the share of checks that came back Ok against what the run required. | A run short of the required share did not pass, even if its State shows Completed. |
| Validation | An icon shown only when the run is part of a validation. | Select the icon to open the validation the run belongs to; blank when the run is not part of one. |
| Created | Shows when the run was created. | The table lists runs newest first by this timestamp. |
Controls reference
Packages
Opens the Functional Testing: Packages page.
When to use: Use it when you need to open a package and start or schedule a run, since you cannot launch a run from Run History itself.
Side effects: Navigates away from Run History; makes no change to any run or filter.
All time
Clears any period restriction so the list includes runs from the entire retained history.
When to use: Use it when you are looking for an older run and don't know roughly when it ran.
Side effects: Reloads the run list without a creation-date bound; replaces whichever chip or custom range was previously active.
1h / 4h / 8h / 24h / 7d / 14d / 30d (lookback chips)
Restricts the list to runs created within the selected relative window.
When to use: Use a short chip like 1h or 4h to confirm a run you just started, or a longer one like 7d or 30d to review recent history.
Side effects: Reloads the list immediately with the new window applied; turns off All time and any custom range.
Custom
Opens a specific start and end date range for the Created filter, prefilled with the last 7 days.
When to use: Use it when you need an exact date range rather than a fixed lookback chip, for example to match an incident window.
Side effects: Applies the chosen range immediately once set; the range cannot reach further back than the configured run retention (180 days by default).
Change
Opens the Configuration: Functional Testing: Retention page where the run and screenshot retention windows are configured.
When to use: Use it when you need to extend how long runs or screenshots are kept, for example before they age out of a Custom date range.
Side effects: Navigates away from Run History; only Global Admin, Infrastructure Admin, or Ops roles can change the values there.
Go to Packages
Opens the Functional Testing: Packages page, shown while the run list is empty.
When to use: Use it the first time you land here with no run history yet, to open a package and run one of its projects or set up a schedule.
Side effects: Navigates away from Run History; makes no change to any data.
Clear filters
Resets every filter, Package, Project, State, Verdict, Engine, Trigger, Gold image, Image version, and the Created period, back to its default.
When to use: Use it after a focused search to return to the full run history without resetting each filter by hand.
Side effects: Reloads the list with no filters applied; does not change or delete any run.
Retry
Reloads the run list after a failed load.
When to use: Use it if the page shows Couldn't load the runs instead of the table.
Side effects: Re-issues the same filtered request; makes no change to any run.
Clear (selection)
Clears every row currently selected for bulk deletion.
When to use: Use it if you selected the wrong runs before confirming a delete.
Side effects: Deselects all rows and disables itself; does not delete anything.
Delete selected runs
Permanently deletes the selected ended runs, along with their steps, screenshots, log, and reports.
When to use: Use it to remove ended runs (Completed, Cancelled, TimedOut, Interrupted, or Error) you no longer need to keep.
Side effects: Irreversibly deletes the selected runs' data; stays disabled with nothing selected and for accounts that do not hold the Functional Testing Admin role.
Previous
Moves the table back one page of runs.
When to use: Use it to step back through pages of 25 runs after moving forward with Next.
Side effects: Reloads the list with the previous page's results; disabled on the first page.
Next
Moves the table forward one page of runs.
When to use: Use it to see older runs beyond the first 25 matching the current filters.
Side effects: Reloads the list with the next page's results; disabled on the last page.
Dismiss
Closes a status message banner, for example after a delete.
When to use: Use it once you've read the message and want it off the page.
Side effects: Hides the banner only; does not undo whatever the message reported.
Verify the result
When runs exist and your filters match them, the table lists matching runs newest first, with columns for Package, Project, State, Verdict, Engine, Trigger, Version, Checks, and Created. Selecting a row opens that run's detail with its steps, screenshots, log, and reports. If the table still shows No runs yet or an unexpectedly short list, the first thing to check is whether the Created period is set to a narrow chip like 1h instead of All time or a wider window, and whether Package or Project is set to a value that excludes the run you expect. If a run genuinely has not been executed yet, open a package from the Packages button and run one of its projects or set up a schedule.
Troubleshooting
- Symptom: No runs appear even though tests have run recently. Fix: Check that the Created filter is not set to a narrow chip like 1h; select All time or a wider chip such as 7d or 30d.
- Symptom: Delete selected runs stays disabled after selecting rows. Fix: Your account role (Operator or Analyst) may not hold the Functional Testing Admin permission the delete action requires; ask an administrator to delete the runs or grant that role.
- Symptom: The Project filter doesn't seem to match what you typed. Fix: Project matches the exact project name, not a partial match; check for typos and give it a short pause after typing, or press Enter to apply at once.
- Symptom: The Change link next to Retention opens a page you can't edit. Fix: Only the Global Admin, Infrastructure Admin, or Ops role can change retention on the Functional Testing: Retention configuration page; other roles can view it only.
Related articles
- Prerequisite: Functional Testing: Packages - a package and its project must be run or scheduled before any run appears in this history
- See also: Functional Testing: Schedules - schedules are the other common way runs in this history get created, reflected in the Trigger filter
- See also: Functional Testing: Engines - the Engine filter and column refer to engines configured there
- See also: Testing: Gold Images (sign-in required) - the gold images and versions the Gold image and Image version filters list
- Next step: Configuration: Functional Testing: Retention - the Change link next to the Retention line opens this page to adjust how long runs and screenshots are kept