-
Notifications
You must be signed in to change notification settings - Fork 29
Capabilities
- app
- files
- deviceName
- launchTimeout
- launchDelay
- platformName
- autoLaunch
- debugConnectToRunningApp
-
innerPort(Deprecated in v1.3.0)
The absolute local path to an .appx
file to be installed and launched. Note that this capability is not required if debugConnectToRunningApp
is specified.
e.g., C:\test\app.appx
Dictionary. Each key of the dictionary is "local file path", each corresponding value is "remote file path".
e.g., { 'C:\AppFiles\downloadedPicture.png': 'download\picture.png' }
Name of emulator to use for running test. Note that this capability is not required, if no device name is specified, then a default emulator is used.You can specify only partial name, first emulator that starts with specified deviceName
will be selected. See notes for how to get list of installed emulators.
e.g., Emulator 8.1 WVGA 4 inch 512MB
Maximum timeout in milliseconds, to be waited for application to launch (application is pinged every 0.5 sec).
e.g., 10000
(default)
Launch delay in milliseconds, to be waited to let visuals to initialize after application launched (after successful ping or timeout). Note: use it if the system running emulator is slow.
e.g., 0
(default)
Ignored in desired capabilities. Set to WindowsPhone
in actual capabilities.
e.g., WindowsPhone
If true
(default), then application will be launch after deployment automatically as part of NewSession
. If false
, then application will not be started automatically and should be started from tests using LaunchApp
command from Appium bindings or using ExecuteScript
command with mobile: App.Open
value.
e.g., true
(default) or false
If true
, then application deployment steps are skipped. Driver assumes that emulator (specified by deviceName
) is already running. app
capability should be set, as ProductId
will be read from app manifest inside app package. This ProductId
will used to locate and launch app on device. If AutoLaunch
is set to true
, then app will be launched, regardless of debugConnectToRunningApp
or app already being launched, this might have side effects.
e.g., true
or false
Depricated in v1.3.0 as part of #39. Starting form v1.3.0 the
innerPort
is set dynamically to ease parallel testing.
In versions below v1.3.0:
Inner driver port used to communicate between OuterDriver and InnerDrive (injected into Windows Phone app). Note: Required only if non-default port was specified in tested app in AutomationServer.Instance.InitializeAndStart
call.
e.g., 9998
(default)
You can obtain list of installed emulators by running:
"C:\Program Files (x86)\Microsoft SDKs\Windows Phone\v8.1\Tools\AppDeploy\AppDeployCmd.exe" /EnumerateDevices