appium capabilities各个参数含义

小灰灰 2023-02-18 03:25 23阅读 0赞

### 文章目录 ###

![在这里插入图片描述][watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L2FiY251bGw_size_16_color_FFFFFF_t_70]

> 这里官网链接，无需魔法上网 [http://appium.io/docs/en/writing-running-appium/caps/][http_appium.io_docs_en_writing-running-appium_caps]

**想要使 inspector 连接安卓的模拟器或手机需要以下参数**

*  platformName
 *  deviceName
 *  appPackage
 *  appActivity
 *  automationName

**一般写代码脚本需要以下基本参数（本人测安卓机）**

*  platformName
 *  udid（这个是唯一设备 id）
 *  deviceName（名字可以随便填写）
 *  appPackage
 *  appActivity

至于 noReset 这个参数可以设置，接收布尔值，表示测试用例执行完后 app 的 session 信息是否被清除，如果是真，则下一个用例运行时候可以还是保持登录状态

avd 这个参数也可以加，作用是不手动打开模拟器，用代码来打开指定模拟器，它的值是`emulator -list-avds`中的设备名称。可能只支持原生的模拟器

**常规通用参数介绍**

<table> 
 <thead> 
  <tr> 
   <th>Capability</th> 
   <th>Description</th> 
   <th>Values</th> 
  </tr> 
 </thead> 
 <tbody> 
  <tr> 
   <td><code>automationName</code></td> 
   <td>Which automation engine to use</td> 
   <td><code>Appium</code> (default), or <code>UiAutomator2</code>, <code>Espresso</code>, or <code>UiAutomator1</code> for Android, or <code>XCUITest</code> or <code>Instruments</code> for iOS, or <code>YouiEngine</code> for application built with You.i Engine</td> 
  </tr> 
  <tr> 
   <td><code>platformName</code></td> 
   <td>Which mobile OS platform to use</td> 
   <td><code>iOS</code>, <code>Android</code>, or <code>FirefoxOS</code></td> 
  </tr> 
  <tr> 
   <td><code>platformVersion</code></td> 
   <td>Mobile OS version</td> 
   <td>e.g., <code>7.1</code>, <code>4.4</code></td> 
  </tr> 
  <tr> 
   <td><code>deviceName</code></td> 
   <td>The kind of mobile device or emulator to use</td> 
   <td><code>iPhone Simulator</code>, <code>iPad Simulator</code>, <code>iPhone Retina 4-inch</code>, <code>Android Emulator</code>, <code>Galaxy S4</code>, etc… On iOS, this should be one of the valid devices returned by instruments with <code>instruments -s devices</code>. On Android this capability is currently ignored, though it remains required.</td> 
  </tr> 
  <tr> 
   <td><code>app</code></td> 
   <td>The absolute local path <em>or</em> remote http URL to a <code>.ipa</code> file (IOS), <code>.app</code> folder (IOS Simulator), <code>.apk</code> file (Android) or <code>.apks</code> file (Android App Bundle), or a <code>.zip</code> 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 <code>appPackage</code> and <code>appActivity</code> capabilities (see below). <code>UiAutomator2</code> and <code>XCUITest</code> allow to start the session without <code>app</code> or <code>appPackage</code>. Incompatible with <code>browserName</code>. See <a href="http://appium.io/docs/en/writing-running-appium/android/android-appbundle/index.html" rel="nofollow">here</a> about <code>.apks</code> file.</td> 
   <td><code>/abs/path/to/my.apk</code> or <code>http://myapp.com/app.ipa</code></td> 
  </tr> 
  <tr> 
   <td><code>otherApps</code></td> 
   <td>App or list of apps (as a JSON array) to install prior to running tests. Note that it will not work with <code>automationName</code> of <code>Espresso</code> and iOS real devices</td> 
   <td>e.g., <code>"/path/to/app.apk"</code>, <code>https://www.example.com/url/to/app.apk</code>, <code>["http://appium.github.io/appium/assets/TestApp9.4.app.zip", "/path/to/app-b.app"]</code></td> 
  </tr> 
  <tr> 
   <td><code>browserName</code></td> 
   <td>Name of mobile web browser to automate. Should be an empty string if automating an app instead.</td> 
   <td>‘Safari’ for iOS and ‘Chrome’, ‘Chromium’, or ‘Browser’ for Android</td> 
  </tr> 
  <tr> 
   <td><code>newCommandTimeout</code></td> 
   <td>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>e.g. <code>60</code></td> 
  </tr> 
  <tr> 
   <td><code>language</code></td> 
   <td>Language to set for iOS (XCUITest driver only) and Android.</td> 
   <td>e.g. <code>fr</code></td> 
  </tr> 
  <tr> 
   <td><code>locale</code></td> 
   <td>Locale to set for iOS (XCUITest driver only) and Android. <code>fr_CA</code> format for iOS. <code>CA</code> format (country name abbreviation) for Android</td> 
   <td>e.g. <code>fr_CA</code>, <code>CA</code></td> 
  </tr> 
  <tr> 
   <td><code>udid</code></td> 
   <td>Unique device identifier of the connected physical device</td> 
   <td>e.g. <code>1ae203187fc012g</code></td> 
  </tr> 
  <tr> 
   <td><code>orientation</code></td> 
   <td>(Sim/Emu-only) start in a certain orientation</td> 
   <td><code>LANDSCAPE</code> or <code>PORTRAIT</code></td> 
  </tr> 
  <tr> 
   <td><code>autoWebview</code></td> 
   <td>Move directly into Webview context. Default <code>false</code></td> 
   <td><code>true</code>, <code>false</code></td> 
  </tr> 
  <tr> 
   <td><code>noReset</code></td> 
   <td>Don’t reset app state before this session. See <a href="http://appium.io/docs/en/writing-running-appium/other/reset-strategies/index.html" rel="nofollow">here</a> for more details</td> 
   <td><code>true</code>, <code>false</code></td> 
  </tr> 
  <tr> 
   <td><code>fullReset</code></td> 
   <td>Perform a complete reset. See <a href="http://appium.io/docs/en/writing-running-appium/other/reset-strategies/index.html" rel="nofollow">here</a> for more details</td> 
   <td><code>true</code>, <code>false</code></td> 
  </tr> 
  <tr> 
   <td><code>eventTimings</code></td> 
   <td>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 <code>false</code>. To enable, use <code>true</code>. The timings are then reported as <code>events</code> property on response to querying the current session. See the <a href="http://appium.io/docs/en/advanced-concepts/event-timings/index.html" rel="nofollow">event timing docs</a> for the the structure of this response.</td> 
   <td>e.g., <code>true</code></td> 
  </tr> 
  <tr> 
   <td><code>enablePerformanceLogging</code></td> 
   <td>(Web and webview only) Enable Chromedriver’s (on Android) or Safari’s (on iOS) performance logging (default <code>false</code>)</td> 
   <td><code>true</code>, <code>false</code></td> 
  </tr> 
  <tr> 
   <td><code>printPageSourceOnFindFailure</code></td> 
   <td>When a find operation fails, print the current page source. Defaults to <code>false</code>.</td> 
   <td>e.g., <code>true</code></td> 
  </tr> 
  <tr> 
   <td><code>clearSystemFiles</code></td> 
   <td>Delete any generated files at the end of a session. Default to <code>false</code>.</td> 
   <td><code>true</code>, <code>false</code></td> 
  </tr> 
 </tbody> 
</table>

**只针对于使用在安卓上的是这些参数**

<table> 
 <thead> 
  <tr> 
   <th>Capability</th> 
   <th>Description</th> 
   <th>Values</th> 
  </tr> 
 </thead> 
 <tbody> 
  <tr> 
   <td><code>appActivity</code></td> 
   <td>Activity name for the Android activity you want to launch from your package. This often needs to be preceded by a <code>.</code> (e.g., <code>.MainActivity</code> instead of <code>MainActivity</code>). By default this capability is received from the package manifest (action: android.intent.action.MAIN , category: android.intent.category.LAUNCHER)</td> 
   <td><code>MainActivity</code>, <code>.Settings</code></td> 
  </tr> 
  <tr> 
   <td><code>appPackage</code></td> 
   <td>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><code>com.example.android.myApp</code>, <code>com.android.settings</code></td> 
  </tr> 
  <tr> 
   <td><code>appWaitActivity</code></td> 
   <td>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 <code>appActivity</code>. You must set it to the very first focused application activity name in case it is different from the one which is set as <code>appActivity</code> if your capability has <code>appActivity</code> and <code>appPackage</code>. You can also use wildcards (<code>*</code>).</td> 
   <td><code>SplashActivity</code>, <code>SplashActivity,OtherActivity</code>, <code>*</code>, <code>*.SplashActivity</code></td> 
  </tr> 
  <tr> 
   <td><code>appWaitPackage</code></td> 
   <td>Java package of the Android app you want to wait for. By default the value of this capability is the same as for <code>appActivity</code></td> 
   <td><code>com.example.android.myApp</code>, <code>com.android.settings</code></td> 
  </tr> 
  <tr> 
   <td><code>appWaitDuration</code></td> 
   <td>Timeout in milliseconds used to wait for the appWaitActivity to launch (default <code>20000</code>)</td> 
   <td><code>30000</code></td> 
  </tr> 
  <tr> 
   <td><code>deviceReadyTimeout</code></td> 
   <td>Timeout in seconds while waiting for device to become ready</td> 
   <td><code>5</code></td> 
  </tr> 
  <tr> 
   <td><code>allowTestPackages</code></td> 
   <td>Allow to install a test package which has <code>android:testOnly="true"</code> in the manifest. <code>false</code> by default</td> 
   <td><code>true</code> or <code>false</code></td> 
  </tr> 
  <tr> 
   <td><code>androidCoverage</code></td> 
   <td>Fully qualified instrumentation class. Passed to -w in adb shell am instrument -e coverage true -w</td> 
   <td><code>com.my.Pkg/com.my.Pkg.instrumentation.MyInstrumentation</code></td> 
  </tr> 
  <tr> 
   <td><code>androidCoverageEndIntent</code></td> 
   <td>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><code>com.example.pkg.END_EMMA</code></td> 
  </tr> 
  <tr> 
   <td><code>androidDeviceReadyTimeout</code></td> 
   <td>Timeout in seconds used to wait for a device to become ready after booting</td> 
   <td>e.g., <code>30</code></td> 
  </tr> 
  <tr> 
   <td><code>androidInstallTimeout</code></td> 
   <td>Timeout in milliseconds used to wait for an apk to install to the device. Defaults to <code>90000</code></td> 
   <td>e.g., <code>90000</code></td> 
  </tr> 
  <tr> 
   <td><code>androidInstallPath</code></td> 
   <td>The name of the directory on the device in which the apk will be push before install. Defaults to <code>/data/local/tmp</code></td> 
   <td>e.g. <code>/sdcard/Downloads/</code></td> 
  </tr> 
  <tr> 
   <td><code>adbPort</code></td> 
   <td>Port used to connect to the ADB server (default <code>5037</code>)</td> 
   <td><code>5037</code></td> 
  </tr> 
  <tr> 
   <td><code>systemPort</code></td> 
   <td><code>systemPort</code> used to connect to <a href="https://github.com/appium/appium-uiautomator2-server" rel="nofollow">appium-uiautomator2-server</a> or <a href="https://github.com/appium/appium-espresso-driver" rel="nofollow">appium-espresso-driver</a>. The default is <code>8200</code> in general and selects one port from <code>8200</code> to <code>8299</code> for <em>appium-uiautomator2-server</em>, it is <code>8300</code> from <code>8300</code> to <code>8399</code> for <em>appium-espresso-driver</em>. When you run tests in parallel, you must adjust the port to avoid conflicts. Read <a href="https://github.com/appium/appium/blob/master/docs/en/advanced-concepts/parallel-tests.md#parallel-android-tests" rel="nofollow">Parallel Testing Setup Guide</a> for more details.</td> 
   <td>e.g., <code>8201</code></td> 
  </tr> 
  <tr> 
   <td><code>remoteAdbHost</code></td> 
   <td>Optional remote ADB server host</td> 
   <td>e.g.: 192.168.0.101</td> 
  </tr> 
  <tr> 
   <td><code>androidDeviceSocket</code></td> 
   <td>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>e.g., <code>chrome_devtools_remote</code></td> 
  </tr> 
  <tr> 
   <td><code>avd</code></td> 
   <td>Name of avd to launch</td> 
   <td>e.g., <code>api19</code></td> 
  </tr> 
  <tr> 
   <td><code>avdLaunchTimeout</code></td> 
   <td>How long to wait in milliseconds for an avd to launch and connect to ADB (default <code>60000</code>)</td> 
   <td><code>300000</code></td> 
  </tr> 
  <tr> 
   <td><code>avdReadyTimeout</code></td> 
   <td>How long to wait in milliseconds for an avd to finish its boot animations (default <code>120000</code>)</td> 
   <td><code>300000</code></td> 
  </tr> 
  <tr> 
   <td><code>avdArgs</code></td> 
   <td>Additional emulator arguments used when launching an avd</td> 
   <td>e.g., <code>-netfast</code></td> 
  </tr> 
  <tr> 
   <td><code>useKeystore</code></td> 
   <td>Use a custom keystore to sign apks, default <code>false</code></td> 
   <td><code>true</code> or <code>false</code></td> 
  </tr> 
  <tr> 
   <td><code>keystorePath</code></td> 
   <td>Path to custom keystore, default ~/.android/debug.keystore</td> 
   <td>e.g., <code>/path/to.keystore</code></td> 
  </tr> 
  <tr> 
   <td><code>keystorePassword</code></td> 
   <td>Password for custom keystore</td> 
   <td>e.g., <code>foo</code></td> 
  </tr> 
  <tr> 
   <td><code>keyAlias</code></td> 
   <td>Alias for key</td> 
   <td>e.g., <code>androiddebugkey</code></td> 
  </tr> 
  <tr> 
   <td><code>keyPassword</code></td> 
   <td>Password for key</td> 
   <td>e.g., <code>foo</code></td> 
  </tr> 
  <tr> 
   <td><code>chromedriverExecutable</code></td> 
   <td>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><code>/abs/path/to/webdriver</code></td> 
  </tr> 
  <tr> 
   <td><code>chromedriverArgs</code></td> 
   <td>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 <code>--url-base</code>, <code>--port</code>, <code>--adb-port</code>, and <code>--log-path</code>.</td> 
   <td>e.g., <code>["--disable-gpu", "--disable-web-security"]</code></td> 
  </tr> 
  <tr> 
   <td><code>chromedriverExecutableDir</code></td> 
   <td>The absolute path to a directory to look for Chromedriver executables in, for automatic discovery of compatible Chromedrivers. Ignored if <code>chromedriverUseSystemExecutable</code> is <code>true</code></td> 
   <td><code>/abs/path/to/chromedriver/directory</code></td> 
  </tr> 
  <tr> 
   <td><code>chromedriverChromeMappingFile</code></td> 
   <td>The absolute path to a file which maps Chromedriver versions to the minimum Chrome that it supports. Ignored if <code>chromedriverUseSystemExecutable</code> is <code>true</code></td> 
   <td><code>/abs/path/to/mapping.json</code></td> 
  </tr> 
  <tr> 
   <td><code>chromedriverUseSystemExecutable</code></td> 
   <td>If <code>true</code>, bypasses automatic Chromedriver configuration and uses the version that comes downloaded with Appium. Ignored if <code>chromedriverExecutable</code> is set. Defaults to <code>false</code></td> 
   <td>e.g., <code>true</code></td> 
  </tr> 
  <tr> 
   <td><code>autoWebviewTimeout</code></td> 
   <td>Amount of time to wait for Webview context to become active, in ms. Defaults to <code>2000</code></td> 
   <td>e.g. <code>4</code></td> 
  </tr> 
  <tr> 
   <td><code>chromedriverPort</code></td> 
   <td>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>e.g. <code>8000</code></td> 
  </tr> 
  <tr> 
   <td><code>chromedriverPorts</code></td> 
   <td>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>e.g. <code>[8000, [9000, 9005]]</code></td> 
  </tr> 
  <tr> 
   <td><code>ensureWebviewsHavePages</code></td> 
   <td>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 <code>false</code></td> 
   <td>e.g. <code>true</code></td> 
  </tr> 
  <tr> 
   <td><code>webviewDevtoolsPort</code></td> 
   <td>To support the <code>ensureWebviewsHavePages</code> 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 <code>9222</code>, 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>e.g. <code>9543</code></td> 
  </tr> 
  <tr> 
   <td><code>enableWebviewDetailsCollection</code></td> 
   <td>Enables collection of detailed WebView information via <code>/json/version</code> 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 <a href="https://github.com/appium/appium/issues/13918" rel="nofollow">fails</a> for custom web views). Defaults to <code>false</code></td> 
   <td><code>true</code> or <code>false</code></td> 
  </tr> 
  <tr> 
   <td><code>dontStopAppOnReset</code></td> 
   <td>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 <code>dontStopAppOnReset</code> set to <code>true</code>, we will not include the <code>-S</code> flag in the <code>adb shell am start</code> call. With this capability omitted or set to <code>false</code>, we include the <code>-S</code> flag. Default <code>false</code></td> 
   <td><code>true</code> or <code>false</code></td> 
  </tr> 
  <tr> 
   <td><code>unicodeKeyboard</code></td> 
   <td>Enable Unicode input, default <code>false</code></td> 
   <td><code>true</code> or <code>false</code></td> 
  </tr> 
  <tr> 
   <td><code>resetKeyboard</code></td> 
   <td>Reset keyboard to its original state, after running Unicode tests with <code>unicodeKeyboard</code> capability. Ignored if used alone. Default <code>false</code></td> 
   <td><code>true</code> or <code>false</code></td> 
  </tr> 
  <tr> 
   <td><code>noSign</code></td> 
   <td>Skip checking and signing of app with debug keys, will work only with UiAutomator, default <code>false</code></td> 
   <td><code>true</code> or <code>false</code></td> 
  </tr> 
  <tr> 
   <td><code>ignoreUnimportantViews</code></td> 
   <td>Calls the <code>setCompressedLayoutHierarchy()</code> 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 <em>setting</em> as well as a capability. Defaults to <code>false</code></td> 
   <td><code>true</code> or <code>false</code></td> 
  </tr> 
  <tr> 
   <td><code>disableAndroidWatchers</code></td> 
   <td>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 <code>false</code></td> 
   <td><code>true</code> or <code>false</code></td> 
  </tr> 
  <tr> 
   <td><code>chromeOptions</code></td> 
   <td>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><code>chromeOptions: {args: ['--disable-popup-blocking']}</code></td> 
  </tr> 
  <tr> 
   <td><code>recreateChromeDriverSessions</code></td> 
   <td>Kill ChromeDriver session when moving to a non-ChromeDriver webview. Defaults to <code>false</code></td> 
   <td><code>true</code> or <code>false</code></td> 
  </tr> 
  <tr> 
   <td><code>nativeWebScreenshot</code></td> 
   <td>In a web context, use native (adb) method for taking a screenshot, rather than proxying to ChromeDriver. Defaults to <code>false</code></td> 
   <td><code>true</code> or <code>false</code></td> 
  </tr> 
  <tr> 
   <td><code>androidScreenshotPath</code></td> 
   <td>The name of the directory on the device in which the screenshot will be put. Defaults to <code>/data/local/tmp</code></td> 
   <td>e.g. <code>/sdcard/screenshots/</code></td> 
  </tr> 
  <tr> 
   <td><code>autoGrantPermissions</code></td> 
   <td>Have Appium automatically determine which permissions your app requires and grant them to the app on install. Defaults to <code>false</code>. If <code>noReset</code> is <code>true</code>, this capability doesn’t work.</td> 
   <td><code>true</code> or <code>false</code></td> 
  </tr> 
  <tr> 
   <td><code>networkSpeed</code></td> 
   <td>Set the network speed emulation. Specify the maximum network upload and download speeds. Defaults to <code>full</code></td> 
   <td><code>['full','gsm', 'edge', 'hscsd', 'gprs', 'umts', 'hsdpa', 'lte', 'evdo']</code> Check <a href="https://developer.android.com/studio/run/emulator-commandline.html" rel="nofollow">-netspeed option</a> more info about speed emulation for avds</td> 
  </tr> 
  <tr> 
   <td><code>gpsEnabled</code></td> 
   <td>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><code>true</code> or <code>false</code></td> 
  </tr> 
  <tr> 
   <td><code>isHeadless</code></td> 
   <td>Set this capability to <code>true</code> to run the Emulator headless when device display is not needed to be visible. <code>false</code> is the default value. <em>isHeadless</em> is also support for iOS, check XCUITest-specific capabilities.</td> 
   <td>e.g., <code>true</code></td> 
  </tr> 
  <tr> 
   <td><code>adbExecTimeout</code></td> 
   <td>Timeout in milliseconds used to wait for adb command execution. Defaults to <code>20000</code></td> 
   <td>e.g., <code>50000</code></td> 
  </tr> 
  <tr> 
   <td><code>localeScript</code></td> 
   <td>Sets the locale <a href="https://developer.android.com/reference/java/util/Locale" rel="nofollow">script</a></td> 
   <td>e.g., <code>"Cyrl"</code> (Cyrillic)</td> 
  </tr> 
  <tr> 
   <td><code>skipDeviceInitialization</code></td> 
   <td>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 <code>false</code></td> 
   <td><code>true</code> or <code>false</code></td> 
  </tr> 
  <tr> 
   <td><code>chromedriverDisableBuildCheck</code></td> 
   <td>Sets the chromedriver flag <code>--disable-build-check</code> for Chrome webview tests</td> 
   <td><code>true</code> or <code>false</code></td> 
  </tr> 
  <tr> 
   <td><code>skipUnlock</code></td> 
   <td>Skips unlock during session creation. Defaults to <code>false</code></td> 
   <td><code>true</code> or <code>false</code></td> 
  </tr> 
  <tr> 
   <td><code>unlockType</code></td> 
   <td>Unlock the target device with particular lock pattern instead of just waking up the device with a helper app. It works with <code>unlockKey</code> capability. Defaults to undefined. <code>fingerprint</code> 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><code>['pin', 'password', 'pattern', 'fingerprint']</code></td> 
  </tr> 
  <tr> 
   <td><code>unlockKey</code></td> 
   <td>A key pattern to unlock used by <code>unlockType</code>.</td> 
   <td>e.g., ‘1111’</td> 
  </tr> 
  <tr> 
   <td><code>autoLaunch</code></td> 
   <td>Initializing the app under test automatically. Appium does not install/launch the app under test if this is <code>false</code>. Defaults to <code>true</code></td> 
   <td><code>true</code> or <code>false</code></td> 
  </tr> 
  <tr> 
   <td><code>skipLogcatCapture</code></td> 
   <td>Skips to start capturing logcat. It might improve performance such as network. Log related commands will not work. Defaults to <code>false</code>.</td> 
   <td><code>true</code> or <code>false</code></td> 
  </tr> 
  <tr> 
   <td><code>uninstallOtherPackages</code></td> 
   <td>A package, list of packages or <code>*</code> to uninstall package/s before installing apks for test. <code>'*'</code> uninstall all of thrid-party packages except for packages which is necessary for Appium to test such as <code>io.appium.settings</code> or <code>io.appium.uiautomator2.server</code> since Appium already contains the logic to manage them.</td> 
   <td>e.g. <code>"io.appium.example"</code>, <code>["io.appium.example1", "io.appium.example2"]</code>, <code>'*'</code></td> 
  </tr> 
  <tr> 
   <td><code>disableWindowAnimation</code></td> 
   <td>Set device animation scale zero if the value is <code>true</code>. After session is complete, Appium restores the animation scale to it’s original value. Defaults to <code>false</code></td> 
   <td><code>true</code>, <code>false</code></td> 
  </tr> 
  <tr> 
   <td><code>remoteAppsCacheLimit</code></td> 
   <td>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 <code>0</code> to disable caching.</td> 
   <td>e.g. <code>0</code>, <code>5</code>, <code>20</code></td> 
  </tr> 
  <tr> 
   <td><code>buildToolsVersion</code></td> 
   <td>Specify the Android <code>build-tools</code> 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>e.g. <code>'28.0.3'</code></td> 
  </tr> 
  <tr> 
   <td><code>androidNaturalOrientation</code></td> 
   <td>Allow for correct handling of orientation on landscape-oriented devices. Set to <code>true</code> to basically flip the meaning of <code>PORTRAIT</code> and <code>LANDSCAPE</code>. Defaults to <code>false</code></td> 
   <td><code>true</code>, <code>false</code></td> 
  </tr> 
  <tr> 
   <td><code>enforceAppInstall</code></td> 
   <td>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 <code>true</code> will enforce Appium to always install the current application build independently of the currently installed version of it. Defaults to <code>false</code>.</td> 
   <td><code>true</code> , <code>false</code></td> 
  </tr> 
  <tr> 
   <td><code>ignoreHiddenApiPolicyError</code></td> 
   <td>Ignores <code>Security exception: Permission denial</code> 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 <code>false</code>.</td> 
   <td><code>true</code>, <code>false</code></td> 
  </tr> 
  <tr> 
   <td><code>mockLocationApp</code></td> 
   <td>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 <code>null</code> or an empty string, then Appium will skip the mocked location provider setup procedure. Defaults to Appium Setting package identifier (<code>io.appium.settings</code>).</td> 
   <td>e.g., <code>null</code>, <code>io.appium.settings</code>, <code>example.your.app</code></td> 
  </tr> 
  <tr> 
   <td>logcatFormat</td> 
   <td>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 <code>threadtime</code>.</td> 
   <td>e.g., <code>process</code></td> 
  </tr> 
  <tr> 
   <td>logcatFilterSpecs</td> 
   <td>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>e.g., <code>['*:W', 'MyActivity:D']</code> (<code>MyActivity</code> is a tag)</td> 
  </tr> 
 </tbody> 
</table>

苹果的我没有给出，需要的可以去官网查看！

[watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L2FiY251bGw_size_16_color_FFFFFF_t_70]: https://img-blog.csdnimg.cn/20200615224406517.png?x-oss-process=image/watermark,type_ZmFuZ3poZW5naGVpdGk,shadow_10,text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L2FiY251bGw=,size_16,color_FFFFFF,t_70
[http_appium.io_docs_en_writing-running-appium_caps]: http://appium.io/docs/en/writing-running-appium/caps/