Skip to end of metadata
Go to start of metadata

Return to the Product Announcements and Release Notes Blog


Hi Sauce User,

Sauce will be discontinuing support for Selendroid as a backend for Android web testing. As part of this change, Sauce will also be discontinuing support for 'old-style' capabilities for both Android and iOS, but not Desktop testing. Details below:

We currently support two frameworks for Android web testing: Selendroid and Appium. Because Appium is better-maintained and more fully-featured, we are choosing to EOL Selendroid. This consolidation onto Appium will allow us to improve the quality of our service and reduce complexity.

How do I know if I'm using Selendroid or Appium on Android web tests?
Selendroid is currently used when you send tests using old-style capabilities (platform + version + browserName). 
Appium is currently used when you send tests using new-style capabilities (platformName + platformVersion + deviceName + browserName). 


The easiest way to check is to go to the Metadata tab on the Test Details page for a recent Android web test, and check out the "base config" section to see what device capabilities Sauce is receiving. 

How much time do I have to migrate? 
By December 14th (30 days), we will be migrating all Android mobile tests coming in on old-style capabilities to run on Appium instead. Although very unlikely, there's always the possibility of breaking your tests due to potential differences between how Appium and Selendroid handle specific commands. We are not aware of any such issues at present, and expect customers' tests to pass without modification after we make the change to target Appium instead of Selendroid for Android web tests. We do recommend, though, that you run a set of tests with the new-style capabilities now, in advance of the switch, to ensure you will not run into any problems later. We also recommend that you standardize on the new-style capabilities in general, as soon as possible.

By February 14th (90 days), we will be removing the ability to run iOS and Android tests using the old-style capabilities. This will break any iOS and Android tests still coming in via the old-style capabilities. (No changes will be made to the Desktop side.) We will be monitoring and reminding customers that have not made the migration as we come up to the date, but we recommend that your team adopt the new-style capabilities as soon as feasible for your team. 


  • No labels