Note: This capability is optional. If not set and device is running a non-iOS OS, the Appium infrastructure will be used. For iOS devices, refer to this article to determine the infrastructure used. |
Capability | Value | Description |
---|---|---|
autoInstrument | true false (default) | To work with hybrid applications, install the iOS/Android application as instrumented. When set to 'true' the iOS/Android application is instrumented before it is installed. |
sensorInstrument | true | To work with sensor input (for example fingerprint simulation, or image injection) install the iOS/Android application as instrumented. When set to 'true' the iOS/Android application is instrumented before it is installed. |
takesScreenshot | true (default) false | Takes screenshots to display in the report. Relevant only if screenshotOnError is false. |
screenshotOnError | true false (default) | Screenshots for report are generated only for error conditions. This capability takes priority over the takesScreenshot capability. |
scriptName | The script report and report folder names. Note: Script name should not include a blank character. | |
dataReset | true (default) | When re-installing an application all data associated with the application will be deleted and application will start with a clean slate. If set to false - data will not be deleted and the updated application will continue in the context of the existing data. |
baseAppiumBehavior | YES | This capability selects whether to use the basic behavior of Appium in cases that Perfecto offers alternative behavior (may be expanded in the future with different behaviors): YES – An element is considered visible if that element's frame is inside the screen frame and also the element is hittable. |
waitForPageLoad | true | Indicates whether the driver.get(url) method of Selenium returns synchronously, i.e. only after the page is loaded, or asynchronously (default), i.e. immediately after sending the request and before the page is actually loaded in the browser. |
Capability | Value | Description |
---|---|---|
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 ofMainActivity) | |
appPackage | Java package of the Android app you want to run | |
appWaitActivity | Activity name for the Android activity you want to wait for | |
appWaitPackage | Java package of the Android app you want to wait for | |
intentAction | (default android.intent.action.MAIN) | Intent action which will be used to start activity |
intentCategory | (default android.intent.category.LAUNCHER) | Intent category which will be used to start activity |
intentFlags | (default 0x10200000) | Flags that will be used to start activity |
optionalIntentArguments | Additional intent arguments that will be used to start activity. See Intent arguments |
Capability | Value | Description |
---|---|---|
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 | |
processArguments | Arguments to pass to the AUT using instruments | |
language | Sets the iOS device language for the duration of the script | |
locale | Sets the iOS device region settings for the duration of the script |
Note: Both language and locale expect a ‘locale identifier’ as a value. These capabilities are applicable to iOS devices that support the XCUITest framework. |
In addition, Perfecto supports the list of Appium server capabilities. To reference these, click here.