---
title: Version 3.9.0 (Jun 2026)
slug: suite-release-notes/version-390-jun-2026
docTags: 
createdAt: 2026-06-22T07:13:45.914Z
---

**Release Date: 22.06.2026**

# New Features

## Builds

We are introducing **Builds** structure in Testinium Suite to make test execution preparation faster and more controlled.

With this feature, users can create a build in advance under **Project > Builds** and select it when running a plan. A build represents a prepared version of the project for a specific branch and commit, helping reduce repeated preparation steps before execution.

:::hint{type="info"}
After this update, please make sure to create a successful build under **Project > Builds** before running your next Plan, and select the relevant build during Plan execution.
:::

### Highlights

- Create and manage builds at project level
- Select a successful build before running a plan
- Reduce repeated build and initialization overhead
- Track which branch and commit are used in each execution

### Notes

- Only builds with **SUCCESS** status can be used.
- Plans should use a build from the same branch as the selected scenarios.
- If new test code is pushed, a new build should be created before execution.

[Full documentation.](https://docs.testinium.com/suite-documentation/builds)

# Improvements

-  Added a new **Parallel Capacity Usage** card to provide a clearer view of current parallel usage and available execution capacity, and removed obsolete minute usage displays.
- Improved **Execution Detail** page design to provide a clearer and more user-friendly experience.
- Added device registration validation for Appium 2 plans during **Plan Edit > Save** and **Apply** actions. Appium 2 devices are now checked for registration status before saving or applying plan changes, consistent with the validation already performed during **Plan Run**.
- Execution metadata values such as **EXECUTION\_ID**, **TEST\_RESULT\_ID**, and **SCENARIO\_ID** are now accessible from test automation code during execution, allowing users to dynamically generate execution-specific report links or use these identifiers in their test logic.
- Added the **Group Plan** option for Appium 2 plans, aligning plan configuration behavior with other project types and allowing users to manage Appium 2 scenarios in grouped plan structures.
- Improved the **Scenarios** and **Plans** pages with UI/UX refinements that make key actions easier to access, provide a clearer page structure, and create a more consistent experience while creating, managing, and running test scenarios and plans.

# Bug Fixes

- Fixed an issue where System Parameters in Selenium 4 plans were not being saved or displayed correctly.
- Fixed an issue where manually stopped Selenium 4 executions could leave the execution node running. Nodes are now properly terminated after a manual stop action, preventing stuck resources and ensuring cleaner execution handling.
- Fixed an issue where execution reports could not be deleted