Version 2.0.0 | May 2025

release date 16 05 2025 new features a new executor model has been introduced to improve test run stability each test run now launches its own executor container via docker engine parallel execution capacity and overall system stability have been significantly improved hanging processes (e g , ssh sessions) are eliminated after this update, the executor field under company list > company details must be updated with the docker engine ip/hostname the test queue mechanism has been migrated from in memory processing to rabbitmq provides higher scalability and persistent queueing prevents data loss during restarts and improves overall performance for high volume executions appium 2 is now fully supported on the platform, including dedicated libraries for java and gauge frameworks note appium 2 license registration is required for licensing and library access support\@testinium com node reservation has been moved from the hub layer to redis faster reservation processing better data consistency eliminated concurrency issues during heavy load users running tests via testinium cloud plugin can now upload mobile applications directly from testinium enterprise during execution—no need to create upload plans from the cloud interface new scenario execution statuses added new end to end execution statuses processing, reporting, terminating, stopped, unexecuted failed test retry count reporting added users can now view errors separately for each retry attempt in scenarios executed with failed test retry count bug fixes fixed an issue where retry runs were incorrectly triggered even when the first test execution was successful resolved a problem where the plan level parallelism setting was not saved consistently fixed the multiple project selection issue on the dashboard fixed search related errors on the plan page when “all projects” was selected resolved the project filter issue on the test result by period report fixed cloud plugin execution errors related to the dynamic executor & queue migration resolved a db connection concurrency error detected during dynamic executor integration fixed an issue where reports could not be displayed properly