---
title: Version 3.3.0 (Jan 2026)
slug: suite-release-notes/version-330-jan-2026
docTags: 
createdAt: 2026-01-13T07:25:52.533Z
---

**Release Date: 19.01.2026**

## New Features

### Selenium 4 Framework Support

We are introducing **Selenium 4 framework support as a Beta release**, enabling teams to start exploring and validating their web automation tests using the latest Selenium architecture.

This Beta release aligns our platform with Selenium 4’s W3C WebDriver–compliant implementation, offering improved compatibility with modern browsers and a more future-ready automation foundation. While the core functionality is fully operational, the Beta phase allows us to gather user feedback and further refine stability and coverage across different use cases.

To support adoption and onboarding, we have also **added a [Selenium4 Sample Projects](docId\:Eje0chYqDSN8Y6ooYPkjv) to our documentation**. This sample project provides a practical reference for project structure, configuration, and basic test execution, helping users get started quickly and confidently during the Beta period.

We encourage users to try Selenium 4 in non-critical environments and share feedback, which will help shape the general availability release.

## Improvements

- Appium 2 execution videos are now downloadable, allowing users to easily access and share test run recordings.
- The user menu design has been updated to include informative links that provide better visibility into the software and related resources.
- Test executions that were skipped were previously displayed as “Successful” and are now correctly shown as “Skipped” in reports, making it easier to identify executions that did not run.
- Container and Executor logs remain accessible even when a test run is stopped, enabling better analysis and troubleshooting of interrupted executions.
- Improved the test plan deletion behavior to ensure consistency across executions.
  - Deleting a single plan continues to work as expected.
  - Support for deleting multiple plans will be implemented for the new services.
  - When a plan is deleted, any active test executions related to that plan now behave as if a **Stop** action was triggered, ensuring running executions are properly terminated.