As app developers, we frequently release new versions of our applications.
In most cases, users upgrade from an older version rather than installing the app from scratch.
This transition often requires migrating existing user data to ensure the app functions correctly, making upgrade testing a crucial step in development.
By thoroughly testing upgrades, we can confirm that the app continues to work as expected post-update.
App upgrades aren't the only scenario where installing apps during a running session is necessary.
Some applications may depend on other apps to function properly.
If your app interacts with another application—such as pulling data or integrating with its features — it's essential to verify that these dependencies remain intact after an upgrade.
Additionally, there are cases where you might need to delete and reinstall an app during a session.
For example, if you want to test how the app behaves when a user uninstalls and reinstalls it, the mid-session install feature can facilitate this process.
(Re-)Installing apps during a test
Before you can install a new app, or a new version of the app, we encourage you to first upload your .apk/.ipa/.zip file to TestingBot Storage.
Alternatively, you can also specify a URL to an .apk/.ipa/.zip file that is publicly accessible.
During your test, you can use the mobile:installApp command to install the app on the device.
Appium will not automatically launch the app after you installed it during the test. You can launch the app manually using the followings commands after installation: