JavaApp自动化测试系列[v1.0.0][Desired Capabilities]

桃扇骨 2022-11-30 15:46 220阅读 0赞

Appium自动化测试驱动类型\[RemoteWebDriver\]\[AppiumDriver\]\[AndroidDriver\]\[IOSDriver\]

> RemoteWebDriver：该驱动来自于Selenium，它可以使测试的机器和发送测试命令的机器对了开来，通过网络请求完成交互，通常不建议直接使用它，Appium提供了其他更方便的驱动  
> AppiumDriver：继承自RemoteWebDriver，增加了特有的功能  
> AndroidDriver：继承自AppiumDriver，增加了特有的功能  
> IOSDriver：继承自Appium，增加了特有的功能

Appium自动化测试控件类型\[WebElement\]\[MobileElement\]\[AndroidElement\]\[IOSElement\]

> WebElement：可以使用所有的Selenium命令  
> MobileElement：属于Appium，继承自WebElement，增加了特有的功能  
> AndroidElement和IOSElement：实现了WebElement接口方法，增加了特有功能

# [Appium Desired Capabilities][] #

## General Capabilities ##

<table> 
 <thead> 
  <tr> 
   <th align="left">Capability</th> 
   <th align="left">Description</th> 
   <th align="left">Values</th> 
  </tr> 
 </thead> 
 <tbody> 
  <tr> 
   <td align="left">automationName</td> 
   <td align="left">Which automation engine to use</td> 
   <td align="left">Appium (default), or UiAutomator2, Espresso, or UiAutomator1 for Android, or XCUITest or Instruments for iOS, or YouiEngine for application built with You.i Engine</td> 
  </tr> 
  <tr> 
   <td align="left">platformName</td> 
   <td align="left">Which mobile OS platform to use</td> 
   <td align="left">iOS, Android, or FirefoxOS</td> 
  </tr> 
  <tr> 
   <td align="left">platformVersion</td> 
   <td align="left">Mobile OS version</td> 
   <td align="left">e.g., 7.1, 4.4</td> 
  </tr> 
  <tr> 
   <td align="left">deviceName</td> 
   <td align="left">The kind of mobile device or emulator to use</td> 
   <td align="left">iPhone Simulator, iPad Simulator, iPhone Retina 4-inch, Android Emulator, Galaxy S4, etc… On iOS, this should be one of the valid devices returned by instruments with instruments -s devices. On Android this capability is currently ignored, though it remains required.</td> 
  </tr> 
  <tr> 
   <td align="left">app</td> 
   <td align="left">The absolute local path or remote http URL to a .ipa file (IOS), .app folder (IOS Simulator), .apk file (Android) or .apks file (Android App Bundle), or a .zip file containing one of these. Appium will attempt to install this app binary on the appropriate device first. Note that this capability is not required for Android if you specify appPackage and appActivity capabilities (see below). UiAutomator2 and XCUITest allow to start the session without app or appPackage. Incompatible with browserName. See here about .apks file.</td> 
   <td align="left">/abs/path/to/my.apk or http://myapp.com/app.ipa</td> 
  </tr> 
  <tr> 
   <td align="left">otherApps</td> 
   <td align="left">App or list of apps (as a JSON array) to install prior to running tests. Note that it will not work with automationName of Espresso and iOS real devices</td> 
   <td align="left">e.g., “/path/to/app.apk”, https://www.example.com/url/to/app.apk, [“http://appium.github.io/appium/assets/TestApp9.4.app.zip”, “/path/to/app-b.app”]</td> 
  </tr> 
  <tr> 
   <td align="left">browserName</td> 
   <td align="left">Name of mobile web browser to automate. Should be an empty string if automating an app instead.</td> 
   <td align="left">‘Safari’ for iOS and ‘Chrome’, ‘Chromium’, or ‘Browser’ for Android</td> 
  </tr> 
  <tr> 
   <td align="left">newCommandTimeout</td> 
   <td align="left">How long (in seconds) Appium will wait for a new command from the client before assuming the client quit and ending the session</td> 
   <td align="left">e.g. 60</td> 
  </tr> 
  <tr> 
   <td align="left">language</td> 
   <td align="left">Language to set for iOS (XCUITest driver only) and Android.</td> 
   <td align="left">e.g. fr</td> 
  </tr> 
  <tr> 
   <td align="left">locale</td> 
   <td align="left">Locale to set for iOS (XCUITest driver only) and Android. fr_CA format for iOS. CA format (country name abbreviation) for Android</td> 
   <td align="left">e.g. fr_CA, CA</td> 
  </tr> 
  <tr> 
   <td align="left">udid</td> 
   <td align="left">Unique device identifier of the connected physical device</td> 
   <td align="left">e.g. 1ae203187fc012g</td> 
  </tr> 
  <tr> 
   <td align="left">autoWebview</td> 
   <td align="left">Move directly into Webview context. Default false</td> 
   <td align="left">true, false</td> 
  </tr> 
  <tr> 
   <td align="left">noReset</td> 
   <td align="left">Don’t reset app state before this session</td> 
   <td align="left">true, false</td> 
  </tr> 
  <tr> 
   <td align="left">fullReset</td> 
   <td align="left">Perform a complete reset.</td> 
   <td align="left">true, false</td> 
  </tr> 
  <tr> 
   <td align="left">eventTimings</td> 
   <td align="left">Enable or disable the reporting of the timings for various Appium-internal events (e.g., the start and end of each command, etc.). Defaults to false. To enable, use true. The timings are then reported as events property on response to querying the current session.</td> 
   <td align="left">e.g., true</td> 
  </tr> 
  <tr> 
   <td align="left">enablePerformanceLogging</td> 
   <td align="left">(Web and webview only) Enable Chromedriver’s (on Android) or Safari’s (on iOS) performance logging (default false)</td> 
   <td align="left">true, false</td> 
  </tr> 
  <tr> 
   <td align="left">printPageSourceOnFindFailure</td> 
   <td align="left">When a find operation fails, print the current page source. Defaults to false.</td> 
   <td align="left">e.g., true</td> 
  </tr> 
  <tr> 
   <td align="left">clearSystemFiles</td> 
   <td align="left">Delete any generated files at the end of a session. Default to false.</td> 
   <td align="left">true, false</td> 
  </tr> 
  <tr> 
   <td align="left">settings[settingsKey]</td> 
   <td align="left">Update Appium Settings on session creation.</td> 
   <td align="left">e.g., ‘settings[mjpegScalingFactor]’: 10, ‘settings[shouldUseCompactResponses]’: true</td> 
  </tr> 
 </tbody> 
</table>

## Android Only ##

These Capabilities are available only on Android-based drivers like [UiAutomator2][]

<table> 
 <thead> 
  <tr> 
   <th align="left">Capability</th> 
   <th align="left">Description</th> 
   <th align="left">Values</th> 
  </tr> 
 </thead> 
 <tbody> 
  <tr> 
   <td align="left">appActivity</td> 
   <td align="left">Activity name for the Android activity you want to launch from your package. This often needs to be preceded by a . (e.g., .MainActivity instead of MainActivity). By default this capability is received from the package manifest (action: android.intent.action.MAIN , category: android.intent.category.LAUNCHER)</td> 
   <td align="left">MainActivity, .Settings</td> 
  </tr> 
  <tr> 
   <td align="left">appPackage</td> 
   <td align="left">Java package of the Android app you want to run. By default this capability is received from the package manifest (@package attribute value)</td> 
   <td align="left">com.example.android.myApp, com.android.settings</td> 
  </tr> 
  <tr> 
   <td align="left">appWaitActivity</td> 
   <td align="left">Activity name/names, comma separated, for the Android activity you want to wait for. By default the value of this capability is the same as for appActivity. You must set it to the very first focused application activity name in case it is different from the one which is set as appActivity if your capability has appActivity and appPackage. You can also use wildcards (*).</td> 
   <td align="left">SplashActivity, SplashActivity,OtherActivity, *, *.SplashActivity</td> 
  </tr> 
  <tr> 
   <td align="left">appWaitPackage</td> 
   <td align="left">Java package of the Android app you want to wait for. By default the value of this capability is the same as for appActivity</td> 
   <td align="left">com.example.android.myApp, com.android.settings</td> 
  </tr> 
  <tr> 
   <td align="left">appWaitDuration</td> 
   <td align="left">Timeout in milliseconds used to wait for the appWaitActivity to launch (default 20000)</td> 
   <td align="left">30000</td> 
  </tr> 
  <tr> 
   <td align="left">deviceReadyTimeout</td> 
   <td align="left">Timeout in seconds while waiting for device to become ready</td> 
   <td align="left">5</td> 
  </tr> 
  <tr> 
   <td align="left">allowTestPackages</td> 
   <td align="left">Allow to install a test package which has android:testOnly=“true” in the manifest. false by default</td> 
   <td align="left">true or false</td> 
  </tr> 
  <tr> 
   <td align="left">androidCoverage</td> 
   <td align="left">Fully qualified instrumentation class. Passed to -w in adb shell am instrument -e coverage true -w</td> 
   <td align="left">com.my.Pkg/com.my.Pkg.instrumentation.MyInstrumentation</td> 
  </tr> 
  <tr> 
   <td align="left">androidCoverageEndIntent</td> 
   <td align="left">A broadcast action implemented by yourself which is used to dump coverage into file system. Passed to -a in adb shell am broadcast -a</td> 
   <td align="left">com.example.pkg.END_EMMA</td> 
  </tr> 
  <tr> 
   <td align="left">androidDeviceReadyTimeout</td> 
   <td align="left">Timeout in seconds used to wait for a device to become ready after booting</td> 
   <td align="left">e.g., 30</td> 
  </tr> 
  <tr> 
   <td align="left">androidInstallTimeout</td> 
   <td align="left">Timeout in milliseconds used to wait for an apk to install to the device. Defaults to 90000</td> 
   <td align="left">e.g., 90000</td> 
  </tr> 
  <tr> 
   <td align="left">androidInstallPath</td> 
   <td align="left">The name of the directory on the device in which the apk will be push before install. Defaults to /data/local/tmp</td> 
   <td align="left">e.g. /sdcard/Downloads/</td> 
  </tr> 
  <tr> 
   <td align="left">adbPort</td> 
   <td align="left">Port used to connect to the ADB server (default 5037)</td> 
   <td align="left">5037</td> 
  </tr> 
  <tr> 
   <td align="left">systemPort</td> 
   <td align="left">systemPort used to connect to appium-uiautomator2-server or appium-espresso-driver. The default is 8200 in general and selects one port from 8200 to 8299 for appium-uiautomator2-server, it is 8300 from 8300 to 8399 for appium-espresso-driver. When you run tests in parallel, you must adjust the port to avoid conflicts. Read Parallel Testing Setup Guide for more details.</td> 
   <td align="left">e.g., 8201</td> 
  </tr> 
  <tr> 
   <td align="left">remoteAdbHost</td> 
   <td align="left">Optional remote ADB server host</td> 
   <td align="left">e.g.: 192.168.0.101</td> 
  </tr> 
  <tr> 
   <td align="left">androidDeviceSocket</td> 
   <td align="left">Devtools socket name. Needed only when tested app is a Chromium embedding browser. The socket is open by the browser and Chromedriver connects to it as a devtools client.</td> 
   <td align="left">e.g., chrome_devtools_remote</td> 
  </tr> 
  <tr> 
   <td align="left">avd</td> 
   <td align="left">Name of avd to launch</td> 
   <td align="left">e.g., api19</td> 
  </tr> 
  <tr> 
   <td align="left">avdLaunchTimeout</td> 
   <td align="left">How long to wait in milliseconds for an avd to launch and connect to ADB (default 60000)</td> 
   <td align="left">300000</td> 
  </tr> 
  <tr> 
   <td align="left">avdReadyTimeout</td> 
   <td align="left">How long to wait in milliseconds for an avd to finish its boot animations (default 120000)</td> 
   <td align="left">300000</td> 
  </tr> 
  <tr> 
   <td align="left">avdArgs</td> 
   <td align="left">Additional emulator arguments used when launching an avd</td> 
   <td align="left">e.g., -netfast</td> 
  </tr> 
  <tr> 
   <td align="left">useKeystore</td> 
   <td align="left">Use a custom keystore to sign apks, default false</td> 
   <td align="left">true or false</td> 
  </tr> 
  <tr> 
   <td align="left">keystorePath</td> 
   <td align="left">Path to custom keystore, default ~/.android/debug.keystore</td> 
   <td align="left">e.g., /path/to.keystore</td> 
  </tr> 
  <tr> 
   <td align="left">keystorePassword</td> 
   <td align="left">Password for custom keystore</td> 
   <td align="left">e.g., foo</td> 
  </tr> 
  <tr> 
   <td align="left">keyAlias</td> 
   <td align="left">Alias for key</td> 
   <td align="left">e.g., androiddebugkey</td> 
  </tr> 
  <tr> 
   <td align="left">keyPassword</td> 
   <td align="left">Password for key</td> 
   <td align="left">e.g., foo</td> 
  </tr> 
  <tr> 
   <td align="left">chromedriverExecutable</td> 
   <td align="left">The absolute local path to webdriver executable (if Chromium embedder provides its own webdriver, it should be used instead of original chromedriver bundled with Appium)</td> 
   <td align="left">/abs/path/to/webdriver</td> 
  </tr> 
  <tr> 
   <td align="left">chromedriverArgs</td> 
   <td align="left">An array of arguments to be passed to the chromedriver binary when it’s run by Appium. By default no CLI args are added beyond what Appium uses internally (such as --url-base, --port, --adb-port, and --log-path.</td> 
   <td align="left">e.g., ["–disable-gpu", “–disable-web-security”]</td> 
  </tr> 
  <tr> 
   <td align="left">chromedriverExecutableDir</td> 
   <td align="left">The absolute path to a directory to look for Chromedriver executables in, for automatic discovery of compatible Chromedrivers. Ignored if chromedriverUseSystemExecutable is true</td> 
   <td align="left">/abs/path/to/chromedriver/directory</td> 
  </tr> 
  <tr> 
   <td align="left">chromedriverChromeMappingFile</td> 
   <td align="left">The absolute path to a file which maps Chromedriver versions to the minimum Chrome that it supports. Ignored if chromedriverUseSystemExecutable is true</td> 
   <td align="left">/abs/path/to/mapping.json</td> 
  </tr> 
  <tr> 
   <td align="left">chromedriverUseSystemExecutable</td> 
   <td align="left">If true, bypasses automatic Chromedriver configuration and uses the version that comes downloaded with Appium. Ignored if chromedriverExecutable is set. Defaults to false</td> 
   <td align="left">e.g., true</td> 
  </tr> 
  <tr> 
   <td align="left">autoWebviewTimeout</td> 
   <td align="left">Amount of time to wait for Webview context to become active, in ms. Defaults to 2000</td> 
   <td align="left">e.g. 4</td> 
  </tr> 
  <tr> 
   <td align="left">chromedriverPort</td> 
   <td align="left">Numeric port to start Chromedriver on. Note that use of this capability is discouraged as it will cause undefined behavior in case there are multiple webviews present. By default Appium will find a free port.</td> 
   <td align="left">e.g. 8000</td> 
  </tr> 
  <tr> 
   <td align="left">chromedriverPorts</td> 
   <td align="left">A list of valid ports for Appium to use for communication with Chromedrivers. This capability supports multiple webview scenarios. The form of this capability is an array of numeric ports, where array items can themselves be arrays of length 2, where the first element is the start of an inclusive range and the second is the end. By default, Appium will use any free port.</td> 
   <td align="left">e.g. [8000, [9000, 9005]]</td> 
  </tr> 
  <tr> 
   <td align="left">ensureWebviewsHavePages</td> 
   <td align="left">Whether or not Appium should augment its webview detection with page detection, guaranteeing that any webview contexts which show up in the context list have active pages. This can prevent an error if a context is selected where Chromedriver cannot find any pages. Defaults to false</td> 
   <td align="left">e.g. true</td> 
  </tr> 
  <tr> 
   <td align="left">webviewDevtoolsPort</td> 
   <td align="left">To support the ensureWebviewsHavePages feature, it is necessary to open a TCP port for communication with the webview on the device under test. This capability allows overriding of the default port of 9222, in case multiple sessions are running simultaneously (to avoid port clash), or in case the default port is not appropriate for your system.</td> 
   <td align="left">e.g. 9543</td> 
  </tr> 
  <tr> 
   <td align="left">enableWebviewDetailsCollection</td> 
   <td align="left">Enables collection of detailed WebView information via /json/version CDP (Chrome Developer Protocol) endpoint since Appium 1.18.0+. This helps to properly match Chromedriver version which supports the given WebView. Without this flag enabled, Appium tries to guess the version of the WebView based on the version of the corresponding installed package (which usually fails for custom web views). Defaults to false</td> 
   <td align="left">true or false</td> 
  </tr> 
  <tr> 
   <td align="left">dontStopAppOnReset</td> 
   <td align="left">Doesn’t stop the process of the app under test, before starting the app using adb. If the app under test is created by another anchor app, setting this false, allows the process of the anchor app to be still alive, during the start of the test app using adb. In other words, with dontStopAppOnReset set to true, we will not include the -S flag in the adb shell am start call. With this capability omitted or set to false, we include the -S flag. Default false</td> 
   <td align="left">true or false</td> 
  </tr> 
  <tr> 
   <td align="left">unicodeKeyboard</td> 
   <td align="left">Enable Unicode input, default false</td> 
   <td align="left">true or false</td> 
  </tr> 
  <tr> 
   <td align="left">resetKeyboard</td> 
   <td align="left">Reset keyboard to its original state, after running Unicode tests with unicodeKeyboard capability. Ignored if used alone. Default false</td> 
   <td align="left">true or false</td> 
  </tr> 
  <tr> 
   <td align="left">noSign</td> 
   <td align="left">Skip checking and signing of app with debug keys, will work only with UiAutomator, default false</td> 
   <td align="left">true or false</td> 
  </tr> 
  <tr> 
   <td align="left">ignoreUnimportantViews</td> 
   <td align="left">Calls the setCompressedLayoutHierarchy() uiautomator function. This capability can speed up test execution, since Accessibility commands will run faster ignoring some elements. The ignored elements will not be findable, which is why this capability has also been implemented as a toggle-able setting as well as a capability. Defaults to false</td> 
   <td align="left">true or false</td> 
  </tr> 
  <tr> 
   <td align="left">disableAndroidWatchers</td> 
   <td align="left">Disables android watchers that watch for application not responding and application crash, this will reduce cpu usage on android device/emulator. This capability will work only with UiAutomator, default false</td> 
   <td align="left">true or false</td> 
  </tr> 
  <tr> 
   <td align="left">chromeOptions</td> 
   <td align="left">Allows passing chromeOptions capability for ChromeDriver. For more information see <a href="https://sites.google.com/a/chromium.org/chromedriver/capabilities" rel="nofollow">chromeOptions</a></td> 
   <td align="left">chromeOptions: {args: [’–disable-popup-blocking’]}</td> 
  </tr> 
  <tr> 
   <td align="left">recreateChromeDriverSessions</td> 
   <td align="left">Kill ChromeDriver session when moving to a non-ChromeDriver webview. Defaults to false</td> 
   <td align="left">true or false</td> 
  </tr> 
  <tr> 
   <td align="left">nativeWebScreenshot</td> 
   <td align="left">In a web context, use native (adb) method for taking a screenshot, rather than proxying to ChromeDriver. Defaults to false</td> 
   <td align="left">true or false</td> 
  </tr> 
  <tr> 
   <td align="left">androidScreenshotPath</td> 
   <td align="left">The name of the directory on the device in which the screenshot will be put. Defaults to /data/local/tmp</td> 
   <td align="left">e.g. /sdcard/screenshots/</td> 
  </tr> 
  <tr> 
   <td align="left">autoGrantPermissions</td> 
   <td align="left">Have Appium automatically determine which permissions your app requires and grant them to the app on install. Defaults to false. If noReset is true, this capability doesn’t work.</td> 
   <td align="left">true or false</td> 
  </tr> 
  <tr> 
   <td align="left">networkSpeed</td> 
   <td align="left">Set the network speed emulation. Specify the maximum network upload and download speeds. Defaults to full</td> 
   <td align="left">[‘full’,‘gsm’, ‘edge’, ‘hscsd’, ‘gprs’, ‘umts’, ‘hsdpa’, ‘lte’, ‘evdo’] Check <a href="https://developer.android.com/studio/run/emulator-commandline" rel="nofollow">-netspeed option</a> more info about speed emulation for avds</td> 
  </tr> 
  <tr> 
   <td align="left">gpsEnabled</td> 
   <td align="left">Toggle gps location provider for emulators before starting the session. By default the emulator will have this option enabled or not according to how it has been provisioned.</td> 
   <td align="left">true or false</td> 
  </tr> 
  <tr> 
   <td align="left">isHeadless</td> 
   <td align="left">Set this capability to true to run the Emulator headless when device display is not needed to be visible. false is the default value. isHeadless is also support for iOS, check XCUITest-specific capabilities.</td> 
   <td align="left">e.g., true</td> 
  </tr> 
  <tr> 
   <td align="left">adbExecTimeout</td> 
   <td align="left">Timeout in milliseconds used to wait for adb command execution. Defaults to 20000</td> 
   <td align="left">e.g., 50000</td> 
  </tr> 
  <tr> 
   <td align="left">localeScript</td> 
   <td align="left">Sets the locale <a href="https://developer.android.com/reference/java/util/Locale" rel="nofollow">script</a></td> 
   <td align="left">e.g., “Cyrl” (Cyrillic)</td> 
  </tr> 
  <tr> 
   <td align="left">skipDeviceInitialization</td> 
   <td align="left">Skip device initialization which includes i.a.: installation and running of Settings app or setting of permissions. Can be used to improve startup performance when the device was already used for automation and it’s prepared for the next automation. Defaults to false</td> 
   <td align="left">true or false</td> 
  </tr> 
  <tr> 
   <td align="left">chromedriverDisableBuildCheck</td> 
   <td align="left">Sets the chromedriver flag --disable-build-check for Chrome webview tests</td> 
   <td align="left">true or false</td> 
  </tr> 
  <tr> 
   <td align="left">skipUnlock</td> 
   <td align="left">Skips unlock during session creation. Defaults to false</td> 
   <td align="left">true or false</td> 
  </tr> 
  <tr> 
   <td align="left">unlockType</td> 
   <td align="left">Unlock the target device with particular lock pattern instead of just waking up the device with a helper app. It works with unlockKey capability. Defaults to undefined. fingerprint is available only for Android 6.0+ and emulators. Read <a href="https://github.com/appium/appium-android-driver/blob/master/docs/UNLOCK.md" rel="nofollow">unlock doc</a> in android driver.</td> 
   <td align="left">[‘pin’, ‘password’, ‘pattern’, ‘fingerprint’]</td> 
  </tr> 
  <tr> 
   <td align="left">unlockKey</td> 
   <td align="left">A key pattern to unlock used by unlockType.</td> 
   <td align="left">e.g., ‘1111’</td> 
  </tr> 
  <tr> 
   <td align="left">autoLaunch</td> 
   <td align="left">Initializing the app under test automatically. Appium does not install/launch the app under test if this is false. Defaults to true</td> 
   <td align="left">true or false</td> 
  </tr> 
  <tr> 
   <td align="left">skipLogcatCapture</td> 
   <td align="left">Skips to start capturing logcat. It might improve performance such as network. Log related commands will not work. Defaults to false.</td> 
   <td align="left">true or false</td> 
  </tr> 
  <tr> 
   <td align="left">uninstallOtherPackages</td> 
   <td align="left">A package, list of packages or * to uninstall package/s before installing apks for test. ‘*’ uninstall all of thrid-party packages except for packages which is necessary for Appium to test such as io.appium.settings or io.appium.uiautomator2.server since Appium already contains the logic to manage them.</td> 
   <td align="left">e.g. “io.appium.example”, [“io.appium.example1”, “io.appium.example2”], ‘*’</td> 
  </tr> 
  <tr> 
   <td align="left">disableWindowAnimation</td> 
   <td align="left">Set device animation scale zero if the value is true. After session is complete, Appium restores the animation scale to it’s original value. Defaults to false</td> 
   <td align="left">true, false</td> 
  </tr> 
  <tr> 
   <td align="left">remoteAppsCacheLimit</td> 
   <td align="left">Set the maximum number of remote cached apks (default is 10) which are pushed to the device-under-test’s local storage. Caching apks remotely speeds up the execution of sequential test cases, when using the same set of apks, by avoiding the need to be push an apk to the remote file system every time a reinstall is needed. Set this capability to 0 to disable caching.</td> 
   <td align="left">e.g. 0, 5, 20</td> 
  </tr> 
  <tr> 
   <td align="left">buildToolsVersion</td> 
   <td align="left">Specify the Android build-tools version to be something different than the default, which is to use the most recent version. It is helpful to use a non-default version if your environment uses alpha/beta build tools.</td> 
   <td align="left">e.g. ‘28.0.3’</td> 
  </tr> 
  <tr> 
   <td align="left">androidNaturalOrientation</td> 
   <td align="left">Allow for correct handling of orientation on landscape-oriented devices. Set to true to basically flip the meaning of PORTRAIT and LANDSCAPE. Defaults to false</td> 
   <td align="left">true, false</td> 
  </tr> 
  <tr> 
   <td align="left">enforceAppInstall</td> 
   <td align="left">By default application installation is skipped if newer or the same version of this app is already present on the device under test. Setting this option to true will enforce Appium to always install the current application build independently of the currently installed version of it. Defaults to false.</td> 
   <td align="left">true , false</td> 
  </tr> 
  <tr> 
   <td align="left">ignoreHiddenApiPolicyError</td> 
   <td align="left">Ignores Security exception: Permission denial alert and allows to continue the session creation process since Appium 1.18.0+. The error happens when Appium tries to relax <a href="https://developer.android.com/distribute/best-practices/develop/restrictions-non-sdk-interfaces#how_can_i_enable_access_to_non-sdk_interfaces" rel="nofollow">hidden API policy</a>, although some devices with a customized firmware deny such requests. Defaults to false.</td> 
   <td align="left">true, false</td> 
  </tr> 
  <tr> 
   <td align="left">mockLocationApp</td> 
   <td align="left">Sets the package identifier of the app, which is used as a system mock location provider since Appium 1.18.0+. This capability has no effect on emulators. If the value is set to null or an empty string, then Appium will skip the mocked location provider setup procedure. Defaults to Appium Setting package identifier (io.appium.settings).</td> 
   <td align="left">e.g., null, io.appium.settings, example.your.app</td> 
  </tr> 
  <tr> 
   <td align="left">logcatFormat</td> 
   <td align="left">Set the output format for logcat messages since Appium 1.18.0. Supported formats are listed in <a href="https://github.com/appium/appium-adb/blob/master/lib/logcat.js" rel="nofollow">here</a>. Please read <a href="https://developer.android.com/studio/command-line/logcat#outputFormat" rel="nofollow">logcat#outputFormat</a> for more details about each format. Defaults to threadtime.</td> 
   <td align="left">e.g., process</td> 
  </tr> 
  <tr> 
   <td align="left">logcatFilterSpecs</td> 
   <td align="left">Set the output filter rule for logcat messages since Appium 1.18.0. Please read <a href="https://developer.android.com/studio/command-line/logcat#filteringOutput" rel="nofollow">logcat#filteringOutput</a> for more details about the rule. <a href="https://developer.android.com/studio/debug/am-logcat" rel="nofollow">Write and View Logs with Logcat</a> is also helpful.</td> 
   <td align="left">e.g., [’*:W’, ‘MyActivity:D’] (MyActivity is a tag)</td> 
  </tr> 
 </tbody> 
</table>

## UIAutomator (1 & 2) ##

These Capabilities are available on UIA 1 and 2

<table> 
 <thead> 
  <tr> 
   <th align="left">Capability</th> 
   <th align="left">Description</th> 
   <th align="left">Values</th> 
  </tr> 
 </thead> 
 <tbody> 
  <tr> 
   <td align="left">intentAction</td> 
   <td align="left">Intent action which will be used to start activity (default android.intent.action.MAIN)</td> 
   <td align="left">e.g.android.intent.action.MAIN, android.intent.action.VIEW</td> 
  </tr> 
  <tr> 
   <td align="left">intentCategory</td> 
   <td align="left">Intent category which will be used to start activity (default android.intent.category.LAUNCHER)</td> 
   <td align="left">e.g. android.intent.category.LAUNCHER, android.intent.category.APP_CONTACTS</td> 
  </tr> 
  <tr> 
   <td align="left">intentFlags</td> 
   <td align="left">Flags that will be used to start activity (default 0x10200000)</td> 
   <td align="left">e.g. 0x10200000</td> 
  </tr> 
  <tr> 
   <td align="left">optionalIntentArguments</td> 
   <td align="left">Additional intent arguments that will be used to start activity.</td> 
   <td align="left">e.g. --esn &lt;EXTRA_KEY&gt;, --ez &lt;EXTRA_KEY&gt; &lt;EXTRA_BOOLEAN_VALUE&gt;, etc.</td> 
  </tr> 
 </tbody> 
</table>

## UIAutomator2 Only ##

These Capabilities are available only on the [UiAutomator2 Driver][UiAutomator2]

<table> 
 <thead> 
  <tr> 
   <th align="left">Capability</th> 
   <th align="left">Description</th> 
   <th align="left">Values</th> 
  </tr> 
 </thead> 
 <tbody> 
  <tr> 
   <td align="left">appWaitForLaunch</td> 
   <td align="left">Tries to launch the app under test without -W option in session creation. It might help when the session creation does not proceed since shell am start does not respond. Defaults to true.</td> 
   <td align="left">false or true</td> 
  </tr> 
  <tr> 
   <td align="left">disableSuppressAccessibilityService</td> 
   <td align="left">Set FLAG_DONT_SUPPRESS_ACCESSIBILITY_SERVICES to allow existing accessibility service continue to run, and a new one may start for Appium. It helps to test the app under test which has accessibility feature such as TalkBack. Appium will not specify the flag if nothing is provided. The flag requires Android API Level 24+.</td> 
   <td align="left">false or true</td> 
  </tr> 
  <tr> 
   <td align="left">mjpegServerPort</td> 
   <td align="left">If specified this is the local port that will be bound to the appium-uiautomator2-server’s MJPEG screenshot stream. This can be used in conjunction with mjpegScreenshotUrl. It should be a valid integer in range 1025…65535. Defaults to null. e.g. mjpegScreenshotUrl = ‘http://localhost:9200’, mjpegServerPort = 9200</td> 
   <td align="left">any Integer, recommended: 9200…9299 for consistency w/ serverPort range</td> 
  </tr> 
  <tr> 
   <td align="left">skipServerInstallation</td> 
   <td align="left">Skip uiAutomator2 server installation and use uiAutomator2 server from the device. Can be used to improve startup performance when an uiAutomator2 server in proper version is already installed on the device. Defaults to false.</td> 
   <td align="left">false or true</td> 
  </tr> 
  <tr> 
   <td align="left">uiautomator2ServerInstallTimeout</td> 
   <td align="left">Timeout in milliseconds used to wait for an uiAutomator2 server to be installed. Defaults to 20000</td> 
   <td align="left">e.g., 20000</td> 
  </tr> 
  <tr> 
   <td align="left">uiautomator2ServerLaunchTimeout</td> 
   <td align="left">Timeout in milliseconds used to wait for an uiAutomator2 server to launch. Defaults to 20000</td> 
   <td align="left">e.g., 20000</td> 
  </tr> 
  <tr> 
   <td align="left">userProfile</td> 
   <td align="left">Enforce user profile as the given parameter if the value was provided. It should be an integer.</td> 
   <td align="left">e.g., 11</td> 
  </tr> 
 </tbody> 
</table>

## Espresso Only ##

These Capabilities are available only on the [Espresso Driver][]

<table> 
 <thead> 
  <tr> 
   <th align="left">Capability</th> 
   <th align="left">Description</th> 
   <th align="left">Values</th> 
  </tr> 
 </thead> 
 <tbody> 
  <tr> 
   <td align="left">espressoServerLaunchTimeout</td> 
   <td align="left">Timeout in milliseconds used to wait for the Espresso server to launch. Defaults to 30000</td> 
   <td align="left">e.g., 50000</td> 
  </tr> 
  <tr> 
   <td align="left">espressoBuildConfig</td> 
   <td align="left">Path to the Espresso server build configuration JSON</td> 
   <td align="left">e.g., /projects/myapp-tests/buildconfig.json</td> 
  </tr> 
  <tr> 
   <td align="left">showGradleLog</td> 
   <td align="left">Whether to pipe Gradle build log for the Espresso server to the Appium log. Defaults to false</td> 
   <td align="left">e.g., true</td> 
  </tr> 
  <tr> 
   <td align="left">skipServerInstallation</td> 
   <td align="left">Skip Espresso server build and apk installation. This option could break proper Espresso server setup for the particular Appium version, but it can improve startup performance when the proper Espresso server and the proper app under test are already installed on the device. Please, make sure not to enable this option if the Espresso server or the application under test needs an update. Defaults to false</td> 
   <td align="left">true or false</td> 
  </tr> 
  <tr> 
   <td align="left">intentOptions</td> 
   <td align="left">Intent options which will be used to start the application under test. It can set intent options such as action, categories and component as JSON format.</td> 
   <td align="left">e.g. {“action”: “android.intent.action.MAIN”, “categories”: “android.intent.category.LAUNCHER”, “component”: “com.appium/.launcher.MainActivity”</td> 
  </tr> 
  <tr> 
   <td align="left">disableSuppressAccessibilityService</td> 
   <td align="left">Set FLAG_DONT_SUPPRESS_ACCESSIBILITY_SERVICES to allow existing accessibility service continue to run, and a new one may start for Appium. It helps to test the app under test which has accessibility feature such as TalkBack. Appium will not specify the flag if nothing is provided. The flag requires Android API Level 24+.</td> 
   <td align="left">true, false</td> 
  </tr> 
  <tr> 
   <td align="left">appLocale</td> 
   <td align="left">Set Locale for the target context since Appium 1.18.0. language, country and variant are available as same as the Locale class. language is mandatory. Please check the locale page for more details. Setting appLocale only affects the locale of the application under test and does not influence other system views, such as the status bar. Consider setting language, locale and/or localeScript capabilities if you would like to change the locale for the entire the system.</td> 
   <td align="left">e.g., {“language”: “ja”, “country”: “JP”}</td> 
  </tr> 
 </tbody> 
</table>

## iOS Only ##

These Capabilities are available only on the [XCUITest Driver][] and the deprecated [UIAutomation Driver][].

<table> 
 <thead> 
  <tr> 
   <th align="left">Capability</th> 
   <th align="left">Description</th> 
   <th align="left">Values</th> 
  </tr> 
 </thead> 
 <tbody> 
  <tr> 
   <td align="left">calendarFormat</td> 
   <td align="left">(Sim-only) Calendar format to set for the iOS Simulator</td> 
   <td align="left">e.g. gregorian</td> 
  </tr> 
  <tr> 
   <td align="left">bundleId</td> 
   <td align="left">Bundle ID of the app under test. Useful for starting an app on a real device or for using other caps which require the bundle ID during test startup. To run a test on a real device using the bundle ID, you may omit the ‘app’ capability, but you must provide ‘udid’.</td> 
   <td align="left">e.g. io.appium.TestApp</td> 
  </tr> 
  <tr> 
   <td align="left">udid</td> 
   <td align="left">Unique device identifier of the connected physical device</td> 
   <td align="left">e.g. 1ae203187fc012g</td> 
  </tr> 
  <tr> 
   <td align="left">launchTimeout</td> 
   <td align="left">Amount of time in ms to wait for instruments before assuming it hung and failing the session</td> 
   <td align="left">e.g. 20000</td> 
  </tr> 
  <tr> 
   <td align="left">locationServicesEnabled</td> 
   <td align="left">(Sim-only) Force location services to be either on or off. Default is to keep current sim setting.</td> 
   <td align="left">true or false</td> 
  </tr> 
  <tr> 
   <td align="left">locationServicesAuthorized</td> 
   <td align="left">(Sim-only) Set location services to be authorized or not authorized for app via plist, so that location services alert doesn’t pop up. Default is to keep current sim setting. Note that if you use this setting you MUST also use the bundleId capability to send in your app’s bundle ID.</td> 
   <td align="left">true or false</td> 
  </tr> 
  <tr> 
   <td align="left">autoAcceptAlerts</td> 
   <td align="left">Accept all iOS alerts automatically if they pop up. This includes privacy access permission alerts (e.g., location, contacts, photos). Default is false.</td> 
   <td align="left">true or false</td> 
  </tr> 
  <tr> 
   <td align="left">autoDismissAlerts</td> 
   <td align="left">Dismiss all iOS alerts automatically if they pop up. This includes privacy access permission alerts (e.g., location, contacts, photos). Default is false.</td> 
   <td align="left">true or false</td> 
  </tr> 
  <tr> 
   <td align="left">nativeInstrumentsLib</td> 
   <td align="left">Use native intruments lib (ie disable instruments-without-delay).</td> 
   <td align="left">true or false</td> 
  </tr> 
  <tr> 
   <td align="left">nativeWebTap</td> 
   <td align="left">Enable “real”, non-javascript-based web taps in Safari. Default: false. Warning: depending on viewport size/ratio; this might not accurately tap an element</td> 
   <td align="left">true or false</td> 
  </tr> 
  <tr> 
   <td align="left">safariInitialUrl</td> 
   <td align="left">Initial safari url, default is a local welcome page</td> 
   <td align="left">e.g. https://www.github.com</td> 
  </tr> 
  <tr> 
   <td align="left">safariAllowPopups</td> 
   <td align="left">(Sim-only) Allow javascript to open new windows in Safari. Default keeps current sim setting</td> 
   <td align="left">true or false</td> 
  </tr> 
  <tr> 
   <td align="left">safariIgnoreFraudWarning</td> 
   <td align="left">(Sim-only) Prevent Safari from showing a fraudulent website warning. Default keeps current sim setting.</td> 
   <td align="left">true or false</td> 
  </tr> 
  <tr> 
   <td align="left">safariOpenLinksInBackground</td> 
   <td align="left">(Sim-only) Whether Safari should allow links to open in new windows. Default keeps current sim setting.</td> 
   <td align="left">true or false</td> 
  </tr> 
  <tr> 
   <td align="left">keepKeyChains</td> 
   <td align="left">(Sim-only) Whether to keep keychains (Library/Keychains) when appium session is started/finished</td> 
   <td align="left">true or false</td> 
  </tr> 
  <tr> 
   <td align="left">localizableStringsDir</td> 
   <td align="left">Where to look for localizable strings. Default en.lproj</td> 
   <td align="left">en.lproj</td> 
  </tr> 
  <tr> 
   <td align="left">processArguments</td> 
   <td align="left">Arguments to pass to the AUT using instruments</td> 
   <td align="left">e.g., -myflag</td> 
  </tr> 
  <tr> 
   <td align="left">interKeyDelay</td> 
   <td align="left">The delay, in ms, between keystrokes sent to an element when typing.</td> 
   <td align="left">e.g., 100</td> 
  </tr> 
  <tr> 
   <td align="left">showIOSLog</td> 
   <td align="left">Whether to show any logs captured from a device in the appium logs. Default false</td> 
   <td align="left">true or false</td> 
  </tr> 
  <tr> 
   <td align="left">sendKeyStrategy</td> 
   <td align="left">strategy to use to type test into a test field. Simulator default: oneByOne. Real device default: grouped</td> 
   <td align="left">oneByOne, grouped or setValue</td> 
  </tr> 
  <tr> 
   <td align="left">screenshotWaitTimeout</td> 
   <td align="left">Max timeout in sec to wait for a screenshot to be generated. default: 10</td> 
   <td align="left">e.g., 5</td> 
  </tr> 
  <tr> 
   <td align="left">waitForAppScript</td> 
   <td align="left">The ios automation script used to determined if the app has been launched, by default the system wait for the page source not to be empty. The result must be a boolean</td> 
   <td align="left">e.g. true;, target.elements().length &gt; 0;, $.delay(5000); true;</td> 
  </tr> 
  <tr> 
   <td align="left">webviewConnectRetries</td> 
   <td align="left">Number of times to send connection message to remote debugger, to get webview. Default: 8</td> 
   <td align="left">e.g., 12</td> 
  </tr> 
  <tr> 
   <td align="left">appName</td> 
   <td align="left">The display name of the application under test. Used to automate backgrounding the app in iOS 9+.</td> 
   <td align="left">e.g., UICatalog</td> 
  </tr> 
  <tr> 
   <td align="left">customSSLCert</td> 
   <td align="left">(Sim only) Add an SSL certificate to IOS Simulator.</td> 
   <td align="left">e.g.-----BEGIN CERTIFICATE-- —MIIFWjCCBEKg…-----END CERTIFICATE-----</td> 
  </tr> 
  <tr> 
   <td align="left">webkitResponseTimeout</td> 
   <td align="left">(Real device only) Set the time, in ms, to wait for a response from WebKit in a Safari session. Defaults to 5000</td> 
   <td align="left">e.g., 10000</td> 
  </tr> 
  <tr> 
   <td align="left">remoteDebugProxy</td> 
   <td align="left">(Sim only, &lt;= 11.2) If set, Appium sends and receives remote debugging messages through a proxy on either the local port (Sim only, &lt;= 11.2) or a proxy on this unix socket (Sim only &gt;= 11.3) instead of communicating with the iOS remote debugger directly.</td> 
   <td align="left">e.g. 12000 or “/tmp/my.proxy.socket”</td> 
  </tr> 
  <tr> 
   <td align="left">enableAsyncExecuteFromHttps</td> 
   <td align="left">capability to allow simulators to execute asynchronous JavaScript on pages using HTTPS. Defaults to false</td> 
   <td align="left">true or false</td> 
  </tr> 
  <tr> 
   <td align="left">skipLogCapture</td> 
   <td align="left">Skips to start capturing logs such as crash, system, safari console and safari network. It might improve performance such as network. Log related commands will not work. Defaults to false.</td> 
   <td align="left">true or false</td> 
  </tr> 
  <tr> 
   <td align="left">webkitDebugProxyPort</td> 
   <td align="left">(Real device only) Port to which ios-webkit-debug-proxy is connected, during real device tests. Default is 27753.</td> 
   <td align="left">12021</td> 
  </tr> 
  <tr> 
   <td align="left">fullContextList</td> 
   <td align="left">Returns the detailed information on contexts for the get available context command. If this capability is enabled, then each item in the returned contexts list would additionally include WebView title, full URL and the bundle identifier. Defaults to false.</td> 
   <td align="left">true or false</td> 
  </tr> 
 </tbody> 
</table>

## iOS Only, using XCUITest ##

> (For XCUITest-specific capabilities, please refer to the documentation on the [XCUITest Driver repo][] itself.)

## MacDriver Only ##

> (For MacDriver capabilities, please refer to the documentation on the [Appium Mac Driver repo][] itself.)

## You.i Engine Only ##

> (For You.i Engine-specific capabilities, please refer to the documentation on the [You.i Engine driver][] itself.)

## WinAppDriver Only ##

> (For WinAppDriver specific capabilities, please refer to the documentation on the [Appium Windows Driver repo][] itself.)

## Flutter driver only ##

> (For FlutterDriver specific capabilities, examples please refer to the documentation on the [Flutter Driver repo][] itself.)

[Appium Desired Capabilities]: https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/caps.md
[UiAutomator2]: https://github.com/appium/appium/blob/master/docs/en/drivers/android-uiautomator2.md
[Espresso Driver]: https://github.com/appium/appium/blob/master/docs/en/drivers/android-espresso.md
[XCUITest Driver]: https://github.com/appium/appium/blob/master/docs/en/drivers/ios-xcuitest.md
[UIAutomation Driver]: https://github.com/appium/appium/blob/master/docs/en/drivers/ios-uiautomation.md
[XCUITest Driver repo]: https://github.com/appium/appium-xcuitest-driver#desired-capabilities
[Appium Mac Driver repo]: https://github.com/appium/appium-mac-driver#desired-capabilities
[You.i Engine driver]: https://github.com/YOU-i-Labs/appium-youiengine-driver#desired-capabilities
[Appium Windows Driver repo]: https://github.com/appium/appium-windows-driver#windowsdriver-specific-capabilities
[Flutter Driver repo]: https://github.com/truongsinh/appium-flutter-driver#desired-capabilities-for-flutter-driver-only