Appium server capabilities tells Appium how to run automated tests, so you need to know more about them. Official documents:http://appium.io/slate/en/master/?ruby#appium-server-capabilitiesAppium Server CapabilitiesAutomationname:which automation engine is used, the default is AppiumPlatformName:which mobile operating system to use, IOS Android or Firefoxosplatform Version:version of the mobile operating systemDevice Name:use the mobile device or simulator type, such as Android Emulator, to return the correct device via the Instruments-s Devices command under iOS system, use the ADB devices to get the device ID app:Absolute Local path or point to an IPA or apk file, this property is not required for Android if the Apppackage and Appactivity properties are specified. Browsername:for automated testing of IDE mobile Web browsers, such as iOS safari,android for Chrome Chromium or browsernewcommandtimeout:Appium waits for the time-out of a new command sent from the client, appium that the client has exited and terminates the session. AutoLaunch:whether to let Appium install and start the app automatically, default to TrueLanguage:Set Languagelocale:Set LocationUdid:unique device identifier for the linked physical deviceOrientation:specify a specific directionAutowebview:directly into the WebView content, the default is FalseNoReset:do not reset the app state before the session, default to FalseFullreset:Delete the entire emulator folder in iOS, and in the Android ton Forbidden City Uninstall app to reset app status instead of clear data. Appium Server capabilities (Android only)appactivity:testers want the name of the Android activity that starts with care, and usually adds a prefix. " "Apppackage:Java packages for Android apps that you want to run, such as Com.example.android.myAppappwaitactivity:The name of the Android activity you want to wait forAppwaitpackage:The name of the Java package that you want to wait fordevicereadytimeout:timeout time to wait for the device to be ready, in secondsAndroidcoverage:fully qualified instrumentation classenableperformancelogging:let Chromedriver's performance log function, only for Chrome and WebView, default to FalseAndroiddevicesocket:Devtool socket name is required only if the application under test is chromium embedding browser, the browser opens the port and Chromedriver connects to the port as a Devtools clientAVD:launched AVD name (Android virtual device)avdlaunchtimeout:wait time for the AVD to start and link to adb, in milliseconds, default 120000avdreadytimeout:waits for the AVD to complete its boot animation, in milliseconds, the default 120000Avdargs:other emulator parameters used when starting the AVDUsekeystore:use a custom KeyStore to sign the APK, default to FalseKeystorepath:the path to the custom KeyStore, which defaults to ~/.android/debug.keystoreKeyalias:Alias for KeyKeypassword:Key's passwordchromdriverexecutable:Absolute Local path to Webdriver executableautowebviewtimeout:timeout for webview content activation, millisecond units, defaultintentaction:Intent action to start activity (default is Android.intent.action.MAIN)Unicodekeyboard:enable Unicode input, default = Falseignoreunimportantviews: call Functions Uiautomator () and Setcompressedlayouthierarchy (), which can speed up test execution because the accessibility command runs faster when some elements are ignored, ignored elements cannot be found, False by defaultAppium Server capabilities (iOS only)Calendarformat:set the calendar format for the iOS simulator
Bundleid: Bundleid for the application under test Udid:unique Device identifier of the physical device being connectedlaunchtimeout: The timeout length, in milliseconds, before assuming that instruments has hung up and terminated the sessionlocationservicesenabled:force Open or close location service for simulator only, keep current setting by defaultlocationservicesauthorized:(simulator only) the location service is set up via plist authorization or the location service is not authorized, so the Location service warning box will not pop up, keep the current setting by default, note that if you use this setting, you must use the Bundleid propertyAutoacceptalerts:automatically accept when a popup iOS privacy access warning is encountered, false by defaultAutodismissalerts:eject iOS privacy access warning, auto dismiss, default falseNativewebtap:in Safari, enable true non-JavaScript-based Web click, default falseSafariinitialurl:Initialize Safari URL, default is local welcome pagesafariallowpopups: allow JavaScript to open a new window in Safarisafariignorefraudwarning:prevent Safari from displaying a warning about a fraudulent websiteSafariopenlinksinbackground:whether Safari allows links to open in a new windowKeepkeychains:whether to save Keychains when the Appium session starts and terminatesinterkeydelay: the length of time, in milliseconds, between keystrokes sent to an element when typingShowioslog:whether any logs captured from the device are displayed in the Appium logscreenshotwaittimeout:the maximum time to wait for the screenshot to be generated, in seconds, by defaultwaitforappscript: used to determine if the application has been started, iOS automated test script, by default the system waits for the page source code is not empty, the result is a Boolean valueThe parameter format is the same as the previous script:
Many of them may not be used at ordinary times, leaving them for forgetting.
appium--detailed Appium server capabilities
