An automation run is created in Testmo each time your automated tests execute and submit results. Each run captures the full test outcome for that execution: which tests passed or failed, how long they took, which threads ran, and any issues that were found. This article explains how to navigate and work with automation runs in the Testmo UI.
Viewing Automation Runs
The Automation section of your project contains all automation runs submitted to Testmo.
The main page opens with three summary metric cards:
- Runs this week — a breakdown of recent runs showing how many succeeded and how many had failures.
- Most active sources — the sources that have submitted the most runs recently.
- Recently run — a chart of run activity over time, with a monthly change indicator.
Below the metrics, a table lists all runs with the following columns:
- Run — the run name, and the configuration in parentheses if one is linked.
- Source — the automation source the run belongs to (for example, backend-api or frontend-selenium).
- Tags — any tags attached to the run.
- Status — shows Success, Failure, or Running depending on the run's current state. Click this indicator to open a stats popup with a breakdown of passed, failed, and skipped test counts.
- Started — when the run was submitted.
- Elapsed time — the total execution time. Runs still in progress show a live timer.
- Failures — the number of failed tests, shown only when failures exist. Clicking it filters the run's results to show only failures.
Filtering runs
Use the inline search/filter bar above the run list to filter by milestones, sources, or tags. For more options, click the filter icon to open the full filter popup, which also supports filtering by configuration, elapsed time, creator, and more.
The Run View
Clicking a run opens its detail view. The header shows the run name, configuration, and overall pass/fail status. From here you can edit the run, export results, or print the run details.
The run view has three tabs: Summary, Results, and Issues.
Summary
The Summary tab gives an overview of the run's outcome.
The main content area shows:
- A stats chart with the breakdown of passed, failed, skipped, blocked, and other custom statuses.
- Two inline tabs for quickly identifying problem areas: Failures lists the top failing tests, and Slowest tests lists the tests that took the longest to run.
- View all tests and Failures buttons link directly to the full Results view and failure-filtered view respectively.
- Execution — the threads that made up this run. If the run used parallel execution, each thread appears as a separate tab here, letting you review the timing and output of each parallel job independently.
- Run details — shown only when the run includes additional fields or artifacts, such as version numbers, Git commit hashes, or links to CI/CD pipeline logs.
The right sidebar shows:
- About — the run status (Completed, Completed & archived, or Running), creation date, source, linked milestone (if any), tags, and contributors.
- Links — any external links attached to the run.
When a milestone is linked, it appears in the About section as a clickable link. A details icon next to it opens a popup showing the milestone's position in the hierarchy.
Results
The Results tab shows all individual test results for the run.
The layout uses three panes:
- Left pane — tests grouped by folder, reflecting the class or namespace structure of your test suite. You can group the test list by Folder, Status, or Thread using the grouping menu. The filter popup lets you narrow results by status, folder, thread, or test name.
- Center pane — the scrollable list of tests with their status, execution time, and other configured columns. Use the columns button to show or hide columns such as assertions count, file name, thread, and line number.
-
Right pane — opens when you select a test, with the following tabs:
- Properties — the test name, status, elapsed time, file and line reference, and any custom field values submitted with the result.
- Comments — notes and issue links added to this test result (see Linking defects to test results below).
- Context — historical results for this test across previous runs of the same source, useful for spotting recurring failures.
- Issues — a consolidated view of all issues linked to this test across its comments.
- Repository — shown when automation linking is configured, this tab displays the repository test case matched to this automated test.
Issues
The Issues tab provides a run-level view of all defects and issues associated with the run.
It has two sections:
- Issues found during testing — issues linked to individual test results within this run via comments. These represent problems found during this specific execution.
- Issues linked from run's milestone — issues linked to the milestone this run is associated with. These represent known defects tracked at the planning level.
Both sections support searching by issue ID and filtering by status. This tab is useful for getting a complete picture of all defects surfaced or tracked in connection with a run, without having to open individual test results.
Linking Automation Runs to Milestones
Linking a run to a milestone connects it to the broader release, sprint, or testing cycle it belongs to. Once linked, the run appears alongside manual test runs and exploratory sessions within that milestone, and its results contribute to the milestone's overall testing summary.
To link a run to a milestone, open the run and click Edit. In the Edit run dialog, use the Milestone field to select a milestone. You can search by name within the selector and create a new milestone inline using the + icon next to the field. Click Save run to apply the change.
To remove a milestone link, open the same dialog, clear the Milestone field, and save.
You can also edit multiple runs at once. Select the runs on the automation main page and use the edit action from the menu. The bulk edit dialog works the same way.
You can also link milestones automatically from the CLI. Read more about it here.
Auto-Archiving
Testmo automatically archives completed automation runs after a period of time configured by your administrator. Archiving reduces the storage used by old runs by trimming most of the individual test records while keeping the information most useful for historical review.
When a run is archived, Testmo removes passing tests that have no comments and keeps only the first 50 failing tests that have no comments. Any test that has a comment attached is always preserved regardless of its status. The run's overall statistics, elapsed time, source, milestone, tags, fields, artifacts, and links are all retained in full.
As a result, when you open an archived run you will see the full summary statistics and any failures or commented tests, but the complete list of all tests is no longer available.
Archived runs remain visible in the automation main page alongside active runs and can still be opened, viewed, and exported. The run's Status indicator shows an Archived label, and the About section in the right sidebar shows Completed & archived. Clicking the Archived indicator opens a brief explanation of what archiving means for that run.
To find older archived runs, use the milestone, source, or tag filters on the main page to narrow the list.
Linking Defects to Test Results
When a test fails, you can link one or more issues from your issue tracker directly to that test result. This connects the failure to the defect being tracked in your team's external system, making it easy to see which bugs are associated with which automated failures.
Adding an issue link
- Open the automation run and go to the Results tab.
- Click the failing test in the center pane to open the details pane on the right.
- Click the Comments tab in the details pane.
- Click the comment editor at the top of the tab.
- Click + Add in the issue input area within the editor.
- In the add issue popup, select the issue tracker and add the issue ID or name.
- Optionally add a note in the comment area for context.
- Click Add to save.
The comment appears in the list below the editor, with the linked issue displayed as a clickable tag showing the issue ID and status. Clicking the tag opens the issue in your external issue tracker.
Editing and removing issue links
To modify a comment or its linked issues, hover over the comment and click the menu icon, then select Edit. Update the comment text or issue links as needed, then click Save to apply.
To remove a comment entirely, select Delete from the same menu and confirm. Deleted comments remain visible in the list with a note indicating who removed them.
Viewing all issues for a run
The Issues tab on the run view shows all issues linked across all test results under Issues found during testing. This is the fastest way to review every defect found during a run without opening individual tests one by one.