Find a run
The Reports list has one row per pipeline run. This page explains every column, how to find a run, how to open it, and what you can do while a run is still going.
In short
On this page you can
- Search runs by pipeline name, test case name or ID.
- Narrow the list by date range, Report Status and tags.
- Read a run’s result at a glance: passed/total, status, duration, AI notes.
- Stop a running pipeline run, or watch a Device Farm run live.
- Open a report and share its address with a teammate.
How to use it
- Open Report; check the date range button (it starts on This week).
- Type a pipeline or test case name in Search pipeline, test case or ID.
- Use the filter icon for Failed runs or a tag, then sort by Started or Duration.
- Click the row to open the run’s Summary; copy the address bar to share it.
- Come back with the back arrow; Back to the open report returns to the same run.
What each column shows#
One row is one pipeline run, however many test cases and iterations it had. The newest run is on top.
| Column | What it shows |
|---|---|
| ID | The report number. The header of an open report shows it as #123. |
| Pipeline Name | The pipeline as it was named when the run started. A loop chip with a number marks one iteration of a repeated pipeline run; opening it loads all its iterations. |
| Run Env. | Where it ran. Web and desktop: Server, Agent or Local. Mobile: AWS DF (AWS Device Farm), BS (BrowserStack), AGENT (your agent’s emulator or device) or DEVICE FARM (SmartTest Device Farm). |
| Environment | DEV, TEST or PRP, the start page environment the run used. |
| Duration | Wall-clock time from the first test case’s start to the last one’s end, as 1h 2m 5s. ... with a spinner while the run is going. See Duration. |
| Started | Just now, minutes ago, Today or Yesterday with the time, otherwise day/month and time. |
| Triggered By | Auto for a timed (scheduled) run, otherwise the user who started it. System when no user is recorded for the run. |
| Result | Passed test case runs out of the planned total, for example 3/4, coloured like the status. Manual pipelines show passed manual cases out of all. See Result chip. |
| Status | Running, Completed, Failed, Disconnected or New, with an icon. See Run status. |
| Notes | Counts of AI verdicts on the run’s failed steps (Bug, Test/Infra, Flaky), and an amber warning count when steps passed with warnings (“{n} step(s) passed with warnings”). — when there is neither. In MOBILE projects the column is called Watch and shows an eye icon while a Device Farm run is live. |
“Completed” is not the same as “all passed”
The status is Failed when any test case failed. A test case that lost its runner (Disconnected) is counted as failed in the Result chip but does not turn the status to Failed. Always read the Result chip: 4/5 with status Completed means one test case did not finish.
Find a run#
Check the date range
The date button above the list starts on This week (Monday to Sunday). Pick Today, Yesterday, Last Week, This month, Last Month, This Year, Last Year or Custom Range. A run belongs to a range when its first test case started inside it. The choice is remembered in this browser.
Search
Type in Search pipeline, test case or ID. It matches part of the pipeline name or a test case name (ignoring case), or an exact report ID or run ID. A leading
#is ignored, so#123finds report 123. The list updates one second after you stop typing.Filter
Click the filter icon next to the search box. Under Report Status choose All, Failed (runs with at least one failed test case) or Completed (runs with at least one passed test case). Below it, Include or Exclude tags. The icon is highlighted while a filter is on.
Sort
Click a column title: ID, Pipeline Name, Run Env., Environment, Duration, Started or Status. Click again to reverse. Sorting by Duration uses the wall-clock time of the whole run.
The rows you need are on the first page. Show 10, 25 or 100 rows per page at the bottom.
A run with both passed and failed test cases is in both filters
Failed and Completed each look for at least one test case with that result, so a mixed run appears under either. Use Failed to find runs that need attention.
The refresh button next to the date range reloads the list and shows Refreshed when done.
Open a report and share its address#
Click the row
The run opens on its Summary tab. A thin bar at the top shows that it is loading. The address becomes
/report/<run id>.Share the address
Copy the address bar and send it. Anyone with access to the same project opens the same report, also after a page refresh. To send the report to someone without an account, use Share Report.
Go back
Use the back arrow left of the report title, or the browser’s Back button. The list keeps its filters. The report you had open stays loaded: Back to the open report, shown with its name at the top of the list, returns to it without reloading.
If a link cannot be opened, you see “This report couldn’t be opened. It may have been deleted or belong to another project.” and land on the list. Switch to the right project in the top bar and open the link again. See the fix.
While a run is in progress#
A running row has a soft amber background, a spinner in Status and ... in Duration. While any row on the page is running, the list refreshes itself every 2 seconds, and once more 3 seconds after the last run ends. You do not need to press refresh.
A run that has shown Running or New for more than 2 hours is treated as dead and shown as Disconnected. See the 2-hour rule.
Stop a run#
Click the stop control
Pipeline runs that are still going show a stop control next to their Result chip. Dry runs are not listed here and cannot be stopped.
Confirm
The dialog Stop this run? explains what happens: “The case that is running now will finish, then no new case starts and the rest are marked as skipped. Teardown cases still run. A running JMeter load test is not waited for: it is stopped within seconds and its partial results are kept.” Click Stop run.
The row shows Stopping… and the message “Stop requested. The current case will finish, then the run stops.” appears.
Test cases that never started are recorded as failed with the note that the run was stopped by the user, so a stopped run ends as Failed. A stopped run cannot be resumed; run the pipeline again. Anyone with access to the project can stop a run.
Watch a Device Farm run (MOBILE)#
In MOBILE projects, while a run on the SmartTest Device Farm is live, the Watch column shows an eye icon. Click it to open the live device panel (Watching run) on the right. With several devices running, a menu lets you pick the device. The icon and the panel close by themselves when the run ends; after that the column shows AI notes like on the web.
Right after you start a run#
When you start a pipeline and SmartestQA takes you to Report, the report opens by itself as soon as the first results exist.
- Preparing report... covers the page with “Execution started and the first logs are being created. The report will open automatically when it is ready.” If the report is not ready within 10 seconds, the overlay closes and you stay on the list; the run appears there as soon as it starts.
- Queued runs. If the test servers are busy, a banner shows your place: “Next in line for your company” or “{count} run(s) of your company are ahead”, with the waiting time and the pool usage, and “the report opens automatically when the run starts.” Remove from queue cancels the run before it starts.
Can I delete a report?#
No. Reports cannot be deleted from a project, by Admins or Users. They are kept with their step logs and screenshots. If a report must be removed, for example because it captured personal data by mistake, write to info@smartestqa.ai with the project name and the report ID.
If something goes wrong#
Didn’t find your answer?Write to support with your project name and what you see on screen.
info@smartestqa.ai