This dialog box displays the list of mobile devices that have been configured for use by Rapise and lets you create a new profile, modify a profile or make a new profile based on an existing one.
How to Open
You can open this dialog box from two places:
·From the main Rapise Options ribbon.
·From the Mobile Spy tool when you click on the 'Mobile Profiles' ribbon menu entry.
This dialog box has the following menu options:
·Select Profile - This dropdown list lets you select a different mobile profile to be displayed in the dialog.
·Save - This button will save the changes to the current mobile profile.
·Test URL - This button will test the Connection (URL) from Rapise to Appium (which is used to manage the devices) and the connection from Appium to the physical (or simulated) device.
·Duplicate - This button will create a new mobile profile based on the currently viewed one.
·Create - This button will create a new empty mobile profile that you can edit.
·Rename - This button will change the name of the current mobile profile being edited.
·Delete - This button will delete the currently displayed mobile profile. There is no undo, so be careful!
This section lets you enter the URL used to connect to the Appium server which hosts the mobile devices being tested. It is typically of the form:
Where the port number used by Appium is 4723 by default and the /ed/hub suffix is added.
This section has various settings, some of which are used by all mobile devices, some only by simulated devices, some only by physical devices and some are specific to the type of device (iOS vs. Android):
oapp - 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. - Values: /abs/path/to/my.apk or http://myapp.com/app.ipa
obrowserName - Name of mobile web browser to automate. Should be an empty string if automating an app instead. - Values: Safari for iOS and Chrome, Chromium, or Browser for Android
oplatformName - Which mobile OS platform to use - Values: iOS, Android, or FirefoxOS
oplatformVersion - Mobile OS version - Values: e.g., 7.1, 4.4
odeviceName - The kind of mobile device or emulator to use - Values: 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.
oudid - Unique device identifier of the connected physical device - Values: e.g. 1ae203187fc012g
oautomationName - Which automation engine to use - Values: Appium (default) or Selendroid
onewCommandTimeout - How long (in seconds) Appium will wait for a new command from the client before assuming the client quit and ending the session - Values: e.g. 60
oautoLaunch - Whether to have Appium install and launch the app automatically. Default true - Values: true, false
olanguage - (Sim/Emu-only) Language to set for the simulator / emulator - Values: e.g. fr
olocale - (Sim/Emu-only) Locale to set for the simulator / emulator - Values: e.g. fr_CA
oorientation - (Sim/Emu-only) start in a certain orientation - Values: LANDSCAPE or PORTRAIT
oautoWebview - Move directly into Webview context. Default false - Values: true, false
onoReset - Don"t reset app state before this session. Default false - Values: true, false
ofullReset - (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 - Values: true, false
·For Android Only
oappActivity - 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) - Values: MainActivity, .Settings
oappPackage - Java package of the Android app you want to run - Values: com.example.android.myApp, com.android.settings
oappWaitActivity - Activity name for the Android activity you want to wait for - Values: SplashActivity
oappWaitPackage - Java package of the Android app you want to wait for - Values: com.example.android.myApp, com.android.settings
odeviceReadyTimeout - Timeout in seconds while waiting for device to become ready - Values: 5
oandroidCoverage - Fully qualified instrumentation class. Passed to -w in adb shell am instrument -e coverage true -w - Values: com.my.Pkg/com.my.Pkg.instrumentation.MyInstrumentation
oenablePerformanceLogging - (Chrome and webview only) Enable Chromedriver"s performance logging (default false) - Values: true, false
oandroidDeviceReadyTimeout - Timeout in seconds used to wait for a device to become ready after booting - Values: e.g., 30
oandroidDeviceSocket - 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. - Values: e.g., chrome_devtools_remote
oavd - Name of avd to launch - Values: e.g., api19
oavdLaunchTimeout - How long to wait in milliseconds for an avd to launch and connect to ADB (default 120000) - Values: 300000
oavdReadyTimeout - How long to wait in milliseconds for an avd to finish its boot animations (default 120000) - Values: 300000
oavdArgs - Additional emulator arguments used when launching an avd - Values: e.g., -netfast
ouseKeystore - Use a custom keystore to sign apks, default false - Values: true or false
okeystorePath - Path to custom keystore, default ~/.android/debug.keystore - Values: e.g., /path/to.keystore
okeystorePassword - Password for custom keystore - Values: e.g., foo
okeyAlias - Alias for key - Values: e.g., androiddebugkey
okeyPassword - Password for key - Values: e.g., foo
ochromedriverExecutable - 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) - Values: /abs/path/to/webdriver
oautoWebviewTimeout - Amount of time to wait for Webview context to become active, in ms. Defaults to 2000 - Values: e.g. 4
ointentAction - Intent action which will be used to start activity (default android.intent.action.MAIN) - Values: e.g.android.intent.action.MAIN, android.intent.action.VIEW
ointentCategory - Intent category which will be used to start activity (default android.intent.category.LAUNCHER) - Values: e.g. android.intent.category.LAUNCHER, android.intent.category.APP_CONTACTS
ointentFlags - Flags that will be used to start activity (default 0x10200000) - Values: e.g. 0x10200000
ooptionalIntentArguments - Additional intent arguments that will be used to start activity. See Intent arguments - Values: e.g. --esn <EXTRA_KEY>, --ez <EXTRA_KEY> <EXTRA_BOOLEAN_VALUE>, etc.
ounicodeKeyboard - Enable Unicode input, default false - Values: true or false
oresetKeyboard - Reset keyboard to its original state, after running Unicode tests with unicodeKeyboard capability. Ignored if used alone. Default false - Values: true or false
onoSign - Skip checking and signing of app with debug keys, will work only with UiAutomator and not with selendroid, default false - Values: true or false
oignoreUnimportantViews - 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 - Values: true or false
·For iOS Only
ocalendarFormat - (Sim-only) Calendar format to set for the iOS Simulator - Values: e.g. gregorian
obundleId - 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". - Values: e.g. io.appium.TestApp
oudid - Unique device identifier of the connected physical device - Values: e.g. 1ae203187fc012g
olaunchTimeout - Amount of time in ms to wait for instruments before assuming it hung and failing the session - Values: e.g. 20000
olocationServicesEnabled - (Sim-only) Force location services to be either on or off. Default is to keep current sim setting. - Values: true or false
olocationServicesAuthorized - (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. - Values: true or false
oautoAcceptAlerts - Accept iOS privacy access permission alerts (e.g., location, contacts, photos) automatically if they pop up. Default is false. - Values: true or false
onativeInstrumentsLib - Use native intruments lib (ie disable instruments-without-delay). - Values: true or false
osafariIgnoreFraudWarning - (Sim-only) Prevent Safari from showing a fraudulent website warning. Default keeps current sim setting. - Values: true or false
osafariOpenLinksInBackground - (Sim-only) Whether Safari should allow links to open in new windows. Default keeps current sim setting. - Values: true or false
okeepKeyChains - (Sim-only) Whether to keep keychains (Library/Keychains) when appium session is started/finished - Values: true or false
olocalizableStringsDir - Where to look for localizable strings. Default en.lproj - Values: en.lproj
oprocessArguments - Arguments to pass to the AUT using instruments - Values: e.g., -myflag
ointerKeyDelay - The delay, in ms, between keystrokes sent to an element when typing. - Values: e.g., 100
oshowIOSLog - Whether to show any logs captured from a device in the appium logs. Default false - Values: true or false
osendKeyStrategy - strategy to use to type test into a test field. Simulator default: oneByOne. Real device default: "grouped - Values: oneByOne, grouped or setValue
oscreenshotWaitTimeout - Max timeout in sec to wait for a screenshot to be generated. default: 10 - Values: e.g., 5
owaitForAppScript - 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 - Values: e.g. true;, target.elements().length > 0;, "$.delay(5000); true;
Kobiton / SauceLabs Settings
In addition, there are some settings, unique to running Appium mobile device tests through either the SauceLabs or Kobiton cloud platforms:
·Kobiton / Sauce Labs
oaccessKey - This needs to be populated with your Kobiton / SauceLabs cloud access key
ocaptureScreenshots - This can be set to determine if you want to capture screenshots or not
odeviceGroup - The default value is group device belonged to. Group device value could be either: ORGANIZATION or KOBITON. System will filter device in any existing group if you set deviceGroup is empty.
osessionDescription - The description of the session (e.g. "This is an example for iOS web")
osessionName - The name of the session being performed (e.g. "Automation test session on second device")
ousername - This needs to be populated with your Kobiton / SauceLabs username
Browser Stack Settings
In addition, there are some settings, unique to running Appium mobile device tests through the BrowserStack cloud platform:
obrowserstack.appium_version - Use this capability to set the Appium version in your test scripts.
obrowserstack.key - This needs to be populated with your Browserstack cloud access key
obrowserstack.user - This needs to be populated with your Browserstack username
odevice - Specifies a particular mobile device for the test environment.
oos_version - Use this capability to specify the OS version of the device.
orealMobile - Use this flag to test on a physical mobile device.