---
title: Version 3.13.0 (Nov 2026)
slug: suite-release-notes/version-3130-nov-2026
createdAt: 2026-11-09T11:42:58.662Z
---

**Release Date: 10.11.2026**

# Improvements

### Reports Now Show Final Scenario Results Only

When retries are enabled, each scenario now appears once in reports, with the final status it had after all retry attempts. Retry attempts no longer increase the scenario count or affect result distributions, success rates or percentages. If you run a plan with 100 scenarios, reports show results for those 100 scenarios, however many retries ran.

::Image[]{src="https://api.archbee.com/api/optimize/RP8RoPxhAp8jZDWs8V_wZ/64n7c-pH6kVpxg2pvfy6O_image.png" size="40" isUploading="false" width="859" height="225" darkWidth="859" darkHeight="225" showCaption="false"}

Retry details are still available:

- **Report page:** You can choose to include retry attempts on the page.
- **Execution Details:** A separate Retry executions section lists the retry attempts.

::Image[]{src="https://api.archbee.com/api/optimize/RP8RoPxhAp8jZDWs8V_wZ/5nfWkUIWi3F2DmhtHF5P4_image.png" size="30" isUploading="false" width="460" height="310" darkWidth="460" darkHeight="310" showCaption="false"}

- **PDF export:** The main results and charts show final results only. A separate short section shows the total number of retry attempts and their status distribution.

This change applies to executions that run after the release. Reports for earlier executions stay as they were.

:::hint{type="info"}
**Note:&#x20;**&#x41; scenario that runs on more than one environment still gets a separate result for each one. For example, a scenario that runs on Chrome and Firefox has two results, each with its own final status.
:::

### Progress display for All-in-One runs on the Dashboard

All-in-One runs execute scenarios sequentially in a single shared environment. Because of this, scenario-level progress cannot be tracked reliably while the run is in progress. Previously, the Dashboard kept showing the first scenario as running even after later scenarios had started, which suggested the run was stuck.

::Image[]{src="https://api.archbee.com/api/optimize/RP8RoPxhAp8jZDWs8V_wZ/1TkjRLwjPpgeGrITnQYll_image.png" size="40" isUploading="false" width="458" height="272" darkWidth="458" darkHeight="272" showCaption="false"}

The Dashboard no longer shows scenario-level progress for All-in-One runs that are in progress. It shows the total number of scenarios instead, with a tooltip explaining that scenario-level progress becomes available once the run finishes. Results for completed All-in-One runs and progress for One-by-One runs are unchanged.

### File Upload Support for Selenium 4 on Linux

Selenium 4 tests that run on Linux environments can now upload files. Scenarios that send a file to a file input element now run as expected in Testinium Suite, so file-upload flows such as document submission, image upload and data import can be covered in automated Web tests without workarounds.

This brings Selenium 4 on Linux to the same level as other supported web environments for file upload.

### Mobile Test Videos Now Start with the Appium Session

Video recording for mobile test executions now starts when the Appium session begins. Before, videos also included device preparation and waiting time from before the test ran. Recordings now show only the test steps, so you can go through a test without skipping past footage you don’t need.

### New "Provisioning" Status for Executions

Executions now have a Provisioning status between Processing and Running. This status covers the time spent preparing and initializing the execution environment before the tests start. On the dashboard, you can see when an execution is in the Provisioning stage while it starts up.

Before, environment preparation was counted as part of the Running status, so reported execution durations were longer than the time the tests actually took. Execution duration is now measured from the moment the execution moves to Running, so it reflects only the time spent running the tests.

The new status flow is: Waiting → Processing → Provisioning → Running

### Redesigned Execution Result Page

The Execution Result page has a new tabbed layout that gives logs more room and keeps the main actions within reach.

- **Run Details tab:** The information from the old fixed left panel is now in a Run Details tab, in a compact layout. It includes project, plan, scenario, status, run date, runtime, operating system and browser, plus project-specific details such as the device for Appium projects. The execution message also appears here, with a copy button.
- **Full-width logs:** With the left panel gone, log areas use the full page width. Only the log content scrolls. Buttons for copying and for jumping to the top or bottom of the log stay visible while you scroll.
- **Status always visible:** The status badge sits in the tab bar and stays visible on every tab. Click it to see the execution message in a pop-up with a copy button. The pop-up opens over the page and doesn’t move or shrink the logs.
- **Report actions on every tab:** Create public URL and Download report are now next to the breadcrumb at the top, so you can use them from any tab.

# Bug Fixes

### Scenario Selection No Longer Filters Other Tabs in All-in-One Reports

In All-in-One reports, opening a scenario result in the Scenarios tab no longer affects the other tabs. They keep showing results for the whole execution, so you can look at one scenario’s details without losing the execution-level view.

###

