The $cloud:appiumOptionsĬapability would itself be a JSON object, with the following internal keys: Capabilityĭesignating which version of the Appium server is used to host and manage drivers. Vendor prefix (so for HeadSpin it would be headspin, Sauce Labs it would be sauce, andīrowserStack it would be browserstack, to name just a few examples). Label $cloud is not meant to be interpreted literally but instead should be replaced by your In addition to the standard platformName, appium:deviceName, appium:automationName, andĪppium:platformVersion, we recommend adopting the capability $cloud:appiumOptions, where the This is a recommendation only, and notĪ standard, but adopting it will help users to navigate the increased complexity that working withĪppium 2.0 in a cloud environment may bring. Providers support, for consistency across the industry. The Appium team makes the following recommendations in terms of the capabilities service

It is of course up to each service provider how they wish to implement theĭiscovery, installation, and availability of any official or third party drivers or plugins. When managing an Appium cloud, your users may wish to target various independent versions of Appiumĭrivers and plugins.

Appium server capabilities