Version 1.0.1 | Apr 2026
We are excited to announce the official v1.0.1 release of the testinium-appium2-driver library. Going forward, release notes for this driver will be shared regularly to keep our users informed about new features, improvements, and updates.
This milestone version introduces new features such as Uninstall Application and Clear App Data to optimize the application lifecycle during test execution, along with flexible logging management.
Release Date: 10.03.2026
New Features
Uninstall Application & Clear App Data
With this driver update, the “Uninstall Application” and “Clear App Data” options available in Testinium Suite can be actively utilized during test execution.
These capabilities are designed to work in alignment with the Testinium Suite platform and are not standalone driver-level features.
When enabled from the platform UI (Plan Edit > "Uninstall Application" & "Clear App Data" options), these actions are applied automatically as part of the test lifecycle:
- Uninstall Application removes the application after the test completes
- Note: For On-Prem (Enterprise) users, works with Enterprise v2.1.0 or higher.
- Clear App Data ensures the application starts from a clean state before execution
- Note: For On-Prem (Enterprise) users, this feature will be available with Enterprise v2.4.0. While the driver already supports this capability, current Enterprise versions do not yet utilize it.
- For Cloud users, it will be available with Cloud v3.8.0, which is planned to be released soon.
Note: These features are only supported on private (dedicated) mobile devices. Public device pools always enforce application cleanup and do not support preserving app state or data between test runs.
This integration allows application lifecycle management to be controlled directly from the platform without requiring additional configuration in the test code.
Standardized Logging
Logging infrastructure has been updated to use SLF4J, with the purpose of enabling Testinium Suite actions to be logged within the Executor Log. This provides clear visibility into what happens during test execution and allows detailed debugging directly on Testinium Suite. The library no longer enforces a specific logging implementation and works with your existing setup such as Log4j or Logback. Log verbosity can be managed directly through your project’s configuration.
If you are using Log4j, you can control Testinium Suite logs with:
Possible Values:
- log4j.logger.com.testinium → ON / OFF
- log4j.additivity.com.testinium → true / false
If such configuration is not defined in your project, logging can also be controlled via Set System Parameters within Testinium Suite:
- log_enabled = true / false (Command Parameter)
To fully disable/enable logging, both Log4j configuration and log_enabled must be set. If no Log4j configuration exists, setting log_enabled=false or true alone is sufficient.
Usage Example
<dependency>
<groupId>com.testinium</groupId>
<artifactId>testinium-appium2-driver</artifactId>
<version>1.0.1</version>
</dependency>