Android Only

These Capabilities are available only on Android-baseddrivers (like UiAutomator2for example).

appActivity

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)

MainActivity, .Settings

appPackage

Java package of the Android app you want to  run. By default this capability is received from the package manifest  (@package attribute value)

com.example.android.myApp,  com.android.settings

appWaitActivity

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.

SplashActivity, SplashActivity,OtherActivity,  *, *.SplashActivity

appWaitPackage

Java package of the Android app you want to  wait for. By default the value of this capability is the same as for  appActivity

com.example.android.myApp,  com.android.settings

appWaitDuration

Timeout in milliseconds used to wait for the  appWaitActivity to launch (default 20000)

30000

deviceReadyTimeout

Timeout in seconds while waiting for device to  become ready

5

allowTestPackages

Allow to install a test package which has  android:testOnly="true" in the manifest. false by default

true or false

androidCoverage

Fully qualified instrumentation class. Passed  to -w in adb shell am instrument -e coverage true -w

com.my.Pkg/com.my.Pkg.instrumentation.MyInstrumentation

androidCoverageEndIntent

A broadcast action implemented by yourself  which is used to dump coverage into file system. Passed to -a in adb shell am  broadcast -a

com.example.pkg.END_EMMA

androidDeviceReadyTimeout

Timeout in seconds used to wait for a device  to become ready after booting

e.g., 30

androidInstallTimeout

Timeout in milliseconds used to wait for an  apk to install to the device. Defaults to 90000

e.g., 90000

androidInstallPath

The name of the directory on the device in  which the apk will be push before install. Defaults to /data/local/tmp

e.g. /sdcard/Downloads/

adbPort

Port used to connect to the ADB server  (default 5037)

5037

systemPort

systemPort used to connect to appium-uiautomator2-server,  default is 8200 in general and selects one port from 8200 to 8299. When you  run tests in parallel, you must adjust the port to avoid conflicts. Read Parallel  Testing Setup Guide for more details.

e.g., 8201

remoteAdbHost

Optional remote ADB server host

e.g.: 192.168.0.101

androidDeviceSocket

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.

e.g., chrome_devtools_remote

avd

Name of avd to launch

e.g., api19

avdLaunchTimeout

How long to wait in milliseconds for an avd to  launch and connect to ADB (default 120000)

300000

avdReadyTimeout

How long to wait in milliseconds for an avd to  finish its boot animations (default 120000)

300000

avdArgs

Additional emulator arguments used when  launching an avd

e.g., -netfast

useKeystore

Use a custom keystore to sign apks, default  false

true or false

keystorePath

Path to custom keystore, default  ~/.android/debug.keystore

e.g., /path/to.keystore

keystorePassword

Password for custom keystore

e.g., foo

keyAlias

Alias for key

e.g., androiddebugkey

keyPassword

Password for key

e.g., foo

chromedriverExecutable

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)

/abs/path/to/webdriver

chromedriverExecutableDir

The absolute path to a directory to look for  Chromedriver executables in, for automatic discovery of compatible  Chromedrivers. Ignored if chromedriverUseSystemExecutable is true

/abs/path/to/chromedriver/directory

chromedriverChromeMappingFile

The absolute path to a file which maps  Chromedriver versions to the minimum Chrome that it supports. Ignored if  chromedriverUseSystemExecutable is true

/abs/path/to/mapping.json

chromedriverUseSystemExecutable

If true, bypasses automatic Chromedriver  configuration and uses the version that comes downloaded with Appium. Ignored  if chromedriverExecutable is set. Defaults to false

e.g., true

autoWebviewTimeout

Amount of time to wait for Webview context to  become active, in ms. Defaults to 2000

e.g. 4

intentAction

Intent action which will be used to start  activity (default android.intent.action.MAIN)

e.g.android.intent.action.MAIN,  android.intent.action.VIEW

intentCategory

Intent category which will be used to start  activity (default android.intent.category.LAUNCHER)

e.g. android.intent.category.LAUNCHER,  android.intent.category.APP_CONTACTS

intentFlags

Flags that will be used to start activity  (default 0x10200000)

e.g. 0x10200000

optionalIntentArguments

Additional intent arguments that will be used  to start activity. See Intent  arguments

e.g. --esn <EXTRA_KEY>, --ez  <EXTRA_KEY> <EXTRA_BOOLEAN_VALUE>, etc.

dontStopAppOnReset

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

true or false

unicodeKeyboard

Enable Unicode input, default false

true or false

resetKeyboard

Reset keyboard to its original state, after  running Unicode tests with unicodeKeyboard capability. Ignored if used alone.  Default false

true or false

noSign

Skip checking and signing of app with debug  keys, will work only with UiAutomator and not with selendroid, default false

true or false

ignoreUnimportantViews

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

true or false

disableAndroidWatchers

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  and not with selendroid, default false

true or false

chromeOptions

Allows passing chromeOptions capability for  ChromeDriver. For more information see chromeOptions

chromeOptions: {args:  ['--disable-popup-blocking']}

recreateChromeDriverSessions

Kill ChromeDriver session when moving to a  non-ChromeDriver webview. Defaults to false

true or false

nativeWebScreenshot

In a web context, use native (adb) method for  taking a screenshot, rather than proxying to ChromeDriver. Defaults to false

true or false

androidScreenshotPath

The name of the directory on the device in  which the screenshot will be put. Defaults to /data/local/tmp

e.g. /sdcard/screenshots/

autoGrantPermissions

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.

true or false

networkSpeed

Set the network speed emulation. Specify the  maximum network upload and download speeds. Defaults to full

['full','gsm', 'edge', 'hscsd', 'gprs',  'umts', 'hsdpa', 'lte', 'evdo'] Check -netspeed  option more info about speed emulation for avds

gpsEnabled

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.

true or false

isHeadless

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.

e.g., true

uiautomator2ServerLaunchTimeout

Timeout in milliseconds used to wait for an  uiAutomator2 server to launch. Defaults to 20000

e.g., 20000

uiautomator2ServerInstallTimeout

Timeout in milliseconds used to wait for an  uiAutomator2 server to be installed. Defaults to 20000

e.g., 20000

otherApps

App or list of apps (as a JSON array) to  install prior to running tests

e.g., "/path/to/app.apk",  https://www.example.com/url/to/app.apk, ["/path/to/app-a.apk",  "/path/to/app-b.apk"]

adbExecTimeout

Timeout in milliseconds used to wait for adb  command execution. Defaults to 20000

e.g., 50000

localeScript

Sets the locale script

e.g., "Cyrl" (Cyrillic)

 

Appium Desired Capabilities-Android Only的更多相关文章

  1. Appium Desired Capabilities

    Appium Desired Capabilities Desired Capabilities 是由 keys 和 values 组成的 JSON 对象. 举个简单例子: { "platf ...

  2. Appium Desired Capabilities信息配置

    编写APPium脚本,必须要配置Desired Capabilities信息 Desired Capabilities 在启动 session 的时候是必须提供的. Desired Capabilit ...

  3. Appium自动化(4) - Appium Desired Capabilities 参数详解

    如果你还想从头学起Appium,可以看看这个系列的文章哦! https://www.cnblogs.com/poloyy/category/1693896.html Desired Capabilit ...

  4. Appium 工作原理及 Desired Capabilities

    一.Appium工作原理 脚本请求 --> 4723端口appium server --> 解析参数给PC端4724端口 --> 发送给设备4724端口 --> 通过设备472 ...

  5. Appium入门(7)__Appium Desired Capabilities

    Desired Capabilities 是由多个键值对组成,代表移动设备相关信息.由Appium Client向Appium Server发送. 但无论Appium Client使用何种语言,最终是 ...

  6. appium简明教程(7)——Desired Capabilities详解

    Desired Capabilities在启动session的时候是必须提供的. Desired Capabilities本质上是key value的对象,它告诉appium server这样一些事情 ...

  7. Appium Python 三:Desired capabilities

    简介 Desired capabilities 是一些键值对的集合.python里面就采用字典的方式. 客户端将这些键值对发给服务端,告诉服务端我们想要怎么测试.比如,我们可以把 platformNa ...

  8. 移动端自动化测试 -- appium 之Desired Capabilities与 定位控件

    一.Desired Capabilities Desired Capabilities 在启动 session 的时候是必须提供的. Desired Capabilities 本质上是以 key va ...

  9. Appium教程——Desired Capabilities 详解(转自TesterHome)

    Desired Capabilities在启动session的时候是必须提供的. Desired Capabilities本质上是key value的对象,它告诉appium server这样一些事情 ...

  10. Appium基础四:Desired Capabilities详讲

    Desired Capabilities在启动session的时候是必须提供的,先看如下代码: Desired Capabilities本质上是key value的对象,他告诉appium serve ...

随机推荐

  1. 解决Linux:Too many levels of symbolic links

    Too many levels of symbolic links 解决:创建链接时使用绝对路径

  2. 解决Vue跨域问题 : 正向代理与反向代理

    你需要做一个反向代理的东西   ===> 打开你的vue项目的config文件夹下的index.js 找到以下代码 dev: { proxyTable: { '/api': { target: ...

  3. CMake速记

    目录 CMake速记 我的demo 外部构建 基础语法 常用指令 环境变量 一些变量 参考文档 title: CMake速记 date: 2019/11/18 19:17:40 toc: true - ...

  4. POJ 3274/洛谷 1360:Gold Balanced Lineup 黄金阵容平衡

    题目描述 Farmer John's N cows (1 ≤ N ≤ 100,000) share many similarities. In fact, FJ has been able to na ...

  5. PYTHON 100days学习笔记008-4:错误和异常

    目录 Day008_04:python错误和异常 1.语法错误 2.异常 3.异常处理 4.抛出异常 5.用户自定义异常 6.定义清理行为 7.预定义的清理行为 参考文章: python3错误和异常 ...

  6. 使用Dreamweaver制作简单网站

    上课过程中有的同学反应没有听懂,特写此博客,将dreamweaver使用过程,细化到每一步,跟着做就行. 一.安装dreamweaver. 1.dreamweaver免安装版下载地址 链接:https ...

  7. 使用pycharm开发web——django2.1.5(四)视图和模板相关

    刘老师说这块很重要..... 应该是很重要,大概看了一下,这里面关于views中函数作用,大概看来可能就是相应请求,传入数据和跳转,基本功能上貌似这些框架都差不多吧(其实我并没用过3个框架以上.... ...

  8. linux系统调用、库函数和内核函数关系与区别

    看系统调用,还有库函数,以前一直不明白,总是以为 系统调用跟库函数是一样的,但是今天才知道是不一样的. 库函数也就是我们通常所说的应用编程接口API,它其实就是一个函数定义,比如常见read().wr ...

  9. MS SQL 2012表分区

    最近开发一个手机用户统计平台,因为涉及到数据庞大,不得不以一周为单位对统计报表进行分区,所以记录一下,方便以后查看 第一步创建文件分组 对于文件分组共创建了14个,从 xy_group_2014102 ...

  10. 简单分析BeanPostProcessor

    1. 什么是BeanPostProcessorBeanPostProcessor是一个接口,有两个方法,分别是:Object postProcessBeforeInitialization(Objec ...