传递给Appium服务器以开启相应安卓Automation会话的Capabilities的几点说明

Desired Capabilities是由客户端发送给Appium服务器端的用来告诉服务器去启动哪种我们想要的会话的一套键值对集合。当中也有一些键值对是用来在自动化的过程中修改服务器端的行为方式的。比如，我们可以把键为platformName的capability的值设置成iOS来告诉服务器我们想要开启的是一个iOS的会话，而非Anddroid的会话。或者我们可以把键为safariAllowPopups的capability的值设置成true来确保在Safari自动化会话的过程中，我们可以使用JavaScript来弹出一个新窗口。要查看Appium支持的完整的capabilities列表，请查看capabilities doc或以下文档。

请注意以下列表中高亮的项，这些都是必填的项目。当中有以下几点需要注意的：

deviceName ：我无论填写什么值，在我的HTC Incredable S机器上都可以跑通测试，但是这项又是必须要填的。我用得Appium版本是V1.2.2。
app ：如果填写了，appium会在目标机器上安装测试目标app，如果没有的话，会根据appActivity和appPackage去目标机器查找目标app
appPackage : 可以通过sdk自带工具aapt获得
appActivity:同样可以通过以上工具获得。有一点需要注意的是，值可以附加packageName，也可以不附加，也就是说以下两种填写方式都是对的“.NotesList"和”com.example.android.notepad.NotesList"

Appium server capabilities

Capability	Description	Values
`automationName`	Which automation engine to use	`Appium` (default) or `Selendroid`
`platformName`	Which mobile OS platform to use	`iOS`, `Android`, or `FirefoxOS`
`platformVersion`	Mobile OS version	e.g., `7.1`, `4.4`
`deviceName`	The kind of mobile device or emulator to use	`iPhone Simulator`, `iPad Simulator`, `iPhone Retina 4-inch`, `Android Emulator`, `Galaxy S4`, etc…
`app`	The absolute local path or remote http URL to an `.ipa` or `.apk` file, or a `.zip` 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). Incompatible with `browserName`.	`/abs/path/to/my.apk` or `http://myapp.com/app.ipa`
`browserName`	Name of mobile web browser to automate. Should be an empty string if automating an app instead.	‘Safari’ for iOS and ‘Chrome’, ‘Chromium’, or ‘Browser’ for Android
`newCommandTimeout`	How long (in seconds) Appium will wait for a new command from the client before assuming the client quit and ending the session	e.g. `60`
`autoLaunch`	Whether to have Appium install and launch the app automatically. Default `true`	`true`, `false`
`language`	(Sim/Emu-only) Language to set for the simulator / emulator	e.g. `fr`
`locale`	(Sim/Emu-only) Locale to set for the simulator / emulator	e.g. `fr_CA`
`udid`	Unique device identifier of the connected physical device	e.g. `1ae203187fc012g`
`orientation`	(Sim/Emu-only) start in a certain orientation	`LANDSCAPE` or `PORTRAIT`
`autoWebview`	Move directly into Webview context. Default `false`	`true`, `false`
`noReset`	Don’t reset app state before this session. Default `false`	`true`, `false`
`fullReset`	(iOS) Delete the entire simulator folder. (Android) Reset app state by uninstalling app instead of clearing app data. On Android, this will also remove the app after the session is complete. Default `false`	`true`, `false`

ANDROID ONLY

Capability	Description	Values
`appActivity`	Activity name for the Android activity you want to launch from your package	`MainActivity`, `.Settings`
`appPackage`	Java package of the Android app you want to run	`com.example.android.myApp`, `com.android.settings`
`appWaitActivity`	Activity name for the Android activity you want to wait for	`SplashActivity`
`appWaitPackage`	Java package of the Android app you want to wait for	`com.example.android.myApp`, `com.android.settings`
`deviceReadyTimeout`	Timeout in seconds while waiting for device to become ready	`5`
`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`
`enablePerformanceLogging`	(Chrome and webview only) Enable Chromedriver’s performance logging (default `false`)	`true`, `false`
`androidDeviceReadyTimeout`	Timeout in seconds used to wait for a device to become ready after booting	e.g., `30`
`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`
`specialChromedriverSessionArgs`	Custom arguments passed directly to chromedriver in chromeOptions capability. Passed as object which properties depend on a specific webdriver.	e.g., `{'androidDeviceSocket': 'opera_beta_devtools_remote',}`
`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.
`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`

IOS ONLY

Capability	Description	Values
`calendarFormat`	(Sim-only) Calendar format to set for the iOS Simulator	e.g. `gregorian`
`bundleId`	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	e.g. `io.appium.TestApp`
`launchTimeout`	Amount of time in ms to wait for instruments before assuming it hung and failing the session	e.g. `20000`
`locationServicesEnabled`	(Sim-only) Force location services to be either on or off. Default is to keep current sim setting.	`true` or`false`
`locationServicesAuthorized`	(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.	`true` or`false`
`autoAcceptAlerts`	Accept iOS privacy access permission alerts (e.g., location, contacts, photos) automatically if they pop up. Default is false.	`true` or`false`
`nativeInstrumentsLib`	Use native intruments lib (ie disable instruments-without-delay).	`true` or`false`
`nativeWebTap`	(Sim-only) Enable “real”, non-javascript-based web taps in Safari. Default: `false`. Warning: depending on viewport size/ratio this might not accurately tap an element	`true` or`false`
`safariAllowPopups`	(Sim-only) Allow javascript to open new windows in Safari. Default keeps current sim setting	`true` or`false`
`safariIgnoreFraudWarning`	(Sim-only) Prevent Safari from showing a fraudulent website warning. Default keeps current sim setting.	`true` or`false`
`safariOpenLinksInBackground`	(Sim-only) Whether Safari should allow links to open in new windows. Default keeps current sim setting.	`true` or`false`
`keepKeyChains`	(Sim-only) Whether to keep keychains (Library/Keychains) when appium session is started/finished	`true` or`false`
`localizableStringsDir`	Where to look for localizable strings. Default `en.lproj`	`en.lproj`
`processArguments`	Arguments to pass to the AUT using instruments	e.g., `-myflag`
`interKeyDelay`	The delay, in ms, between keystrokes sent to an element when typing.	e.g., `100`

以下是一个配置例子：

    public void setUp() throws Exception {         // set up appium         File classpathRoot = new File(System.getProperty("user.dir"));         File appDir = new File(classpathRoot, "apps");         File app = new File(appDir, "NotePad.apk");         DesiredCapabilities capabilities = new DesiredCapabilities();         capabilities.setCapability("deviceName","iPad Simulator");         //capabilities.setCapability("platformVersion", "4.2");         capabilities.setCapability("platformName", "Android");         capabilities.setCapability("app", app.getAbsolutePath());         //capabilities.setCapability("appPackage", "com.example.android.notepad");         //capabilities.setCapability("appActivity", "com.example.android.notepad.NotesList");         //capabilities.setCapability("appActivity", ".NotesList");         driver = new AppiumDriver(new URL("http://127.0.0.1:4723/wd/hub"), capabilities);     }

作者

自主博客

微信

CSDN

天地会珠海分舵

http://techgogogo.com

服务号:TechGoGoGo

扫描码:

©著作权归作者所有：来自51CTO博客作者zhukev的原创作品，如需转载，请注明出处，否则将追究法律责任

android capabilities appium

上一篇：(转载）AppiumDriver... 下一篇：Appium环境配置笔记2 --...

zhukev

117篇文章，7W+人气，0粉丝

Ctrl+Enter 发布

发布

取消

猜你喜欢

我的友情链接最新HTML BroadcastChannel API引荐简述centOS 7系统用户和组的管理及配置解析DELL R710服务器迁移操作内容开学季出大事：某教育局丢失3台虚拟机 EVA4400存储虚拟机+数据库数据恢复成功案例服务器数据恢复通用方法+服务器分区丢失恢复案例在CentOS7上部署squid缓存服务器及代理功能 EMC 5400服务器raid阵列瘫痪数据恢复成功案例服务器数据恢复案例 / raid5阵列多块硬盘离线处理方法华为存储服务器卷丢失数据恢复成功案例斐讯K3C路由器无需刷机用vlmcsd搭建KMS服务器激活Windows&office 高校服务器虚拟化——高校数据中心建设【长文+图片】HP FC MSA2000服务器瘫痪数据恢复过程服务器断电瘫痪数据丢失后恢复数据的过程华为5800服务器raid阵列数据恢复成功案例【长文慎点】IBM X3850服务器删除并重建虚拟机恢复过程 HP EVA4400服务器RAID信息丢失数据恢复方法 Apache 工作模式的优化深入部署PXE远程安装服务并实现Kickstart无人值守安装

扫一扫,领取大礼包

zhukev

转载于:https://blog.51cto.com/techgogogo/1608454