Skip to content

Latest commit

 

History

History
73 lines (60 loc) · 4.18 KB

platform-support.md

File metadata and controls

73 lines (60 loc) · 4.18 KB
Raw

Appium Platform Support

Appium supports a variety of platforms and testing modalities (native, hybrid, web, real devices, simulators, etc...). This document is designed to make explicit the level of support and requirements for each of these.

iOS Support

iOS automation is supported with two drivers:

Please refer to these driver docs for setup instructions.

  • Versions: 9.0 and up (as a rule, Appium supports the latest two iOS versions)
  • Devices: Simulator and real device for iPhone, iPad and tvOS
  • Native app support: Yes, with debug version of .app (simulator), or correctly-signed .ipa (real devices). Underlying support is provided by Apple's XCUITest (or UIAutomation for older versions) framework.
  • Mobile web support: Yes, via automation of mobile Safari. For real devices, ios-webkit-remote-debugger is required, and automation of native aspects of the Safari interface is not possible. See the mobile web doc for instructions.
  • Hybrid support: Yes. For real devices, ios-webkit-remote-debugger is required. See the hybrid doc for instructions.
  • Support for automating multiple apps in one session: No
  • Support for automating multiple devices simultaneously: No
  • Support for automating vendor-provided or third-party apps: Only vendor-provided apps (Preferences, Maps, etc...), and only on the simulator. For iOS 10+, you can automate the home screen as well.
  • Support for automating custom, non-standard UI controls: Minimal. You need to set accessibility information on the control which enables some basic automation.

Android Support

Android automation is supported with two drivers:

Please refer to these driver docs for setup instructions.

  • Versions: 2.3 and up
  • Devices: Android emulators and real Android devices
  • Native app support: Yes
  • Mobile web support: Yes (but not when using Selendroid backend). Automation is effected using a bundled Chromedriver server as a proxy. With 4.2 and 4.3, automation works on official Chrome browser or Chromium only. With 4.4+, automation also works on the built-in "Browser" app. Chrome/Chromium/Browser must already be installed on the device under test. See the mobile web doc for instructions.
  • Hybrid support: Yes. See the hybrid doc for instructions.
    • With default Appium automation backend: versions 4.4 and up
    • With Selendroid automation backend: versions 2.3 and up
  • Support for automating multiple apps in one session: Yes (but not when using the Selendroid backend)
  • Support for automating multiple devices simultaneously: Yes, though Appium must be started using different ports for the server parameters --port, --bootstrap-port (or --selendroid-port) and/or --chromedriver-port. See the server args doc for more information on these parameters.
  • Support for automating vendor-provided or third-party apps: Yes (but not when using the Selendroid backend)
  • Support for automating custom, non-standard UI controls: No

Windows Desktop Support

See the Windows Driver doc for details