Version 2.1.0 | Feb 2026

release date 19 02 2026 new features all in one execution mode for mobile and web the all in one execution mode is now available for both mobile and web tests in this mode, all selected scenarios run within a single execution session instead of being split into separate runs this enables faster overall execution by reducing repeated setup steps scenarios to be executed in the defined order within the test automation code a continuous execution flow across scenarios all scenarios are executed sequentially under the same session, providing a more streamlined and predictable run behavior https //docs testinium com/suite documentation/dispatch method selenium 4 framework support we are introducing selenium 4 framework support, enabling teams to start exploring and validating their web automation tests using the latest selenium architecture this 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 the updated infrastructure provides more stable driver communication, predictable capability handling, and better long term maintainability for automation projects to support adoption and onboarding, we have also added a 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 start running their selenium 4 tests and share feedback with our team, helping us further enhance coverage and stability across different use cases improvements appium 2 video recording support video recording is now supported for appium 2 tests each test run creates a video showing what happened on the device, so failures can be understood more easily without checking only logs the video is automatically added to the test report and can be watched directly from the results page in the "notification pdf export" feature (plan > edit > schedule & notification), two separate sections have been added to the exported pdf file “overall results” and “scenario results ” the top section includes the overall results of the entire execution to provide a clear summary, while the bottom section displays specific filtered results login performance improvement after login, users are first redirected to the dashboard since the dashboard was loading slowly, it was causing the login process to feel slow as well to improve loading time, the default number of pie charts displayed on the dashboard has been reduced from 4 to 1 only the “today” pie chart is shown by default users can still select 7, 30, or 90 days from the menu if needed added “uninstall application after execution” options to the appium 2 test plan edit screen azure devops user fetch endpoint updated the endpoint parameters used in the azure devops integration user fetch method have been updated this update improves compatibility with azure devops apis and ensures more reliable user synchronization for appium 2 tests, device names appeared in reports using the model identifier (for example, sm a546e) these identifiers are not easily recognizable for most users with this update, device information will now display the market name of the device instead of the model code for example before sm a546e now samsung galaxy a54 this change makes device selection and identification within test plans clearer and more user friendly bug fixes for appium 2 tests, in the previous results screen, the environment value appearing as “?” has been fixed fixed an issue where the right column was not visible in the generated pdf report the report layout now renders correctly with all sections displayed as expected fixed an issue where test execution report > test execution details > list by environment for appium 2 executions was returning a 500 error tests stuck in “running” status previously, the full maven output inside the images was forwarded to the services when a large error occurred during the mvn test compile phase, the error size caused a failure while sending it to the frontend, leaving tests stuck in the running status now, if the test cannot be compiled, a static error message is shown in the ui, and the full error details can be found in the container logs