In this post we will start our discussion on Appium Session and Appium desired capabilities
all the commands (client commands) are executed in the context of a
Clients initiate a session with a server in ways specific to each library, but they all end up sending a POST /session request to the server, with a JSON object called the
At this point the server will start up the automation session and respond with a session ID which is used for sending further commands.
Here is the complete video of the below discussion
Appium Desired capabilities?
Desired Capabilities are sent by the
via JSON Objects by requesting the automation session we need.
These desired capabilities are found in the link below
Appium server Capability
Some of the Appium Server Capability are listed below
Which automation engine to use
Appium (default) or Selendroid
Which mobile OS platform to use
iOS, Android, or FirefoxOS
Mobile OS version
e.g., 7.1, 4.4
The kind of mobile device or emulator to use
iPhone Simulator, iPad Simulator, iPhone Retina 4-inch, Android Emulator, Galaxy S4, etc…
Android only capability
Activity name for the Android activity you want to launch from your package
Java package of the Android app you want to run
Activity name for the Android activity you want to wait for
Java package of the Android app you want to wait for
Timeout in seconds while waiting for device to become ready
Fully qualified instrumentation class. Passed to -w in adb shell am instrument -e coverage true -w
(Chrome and webview only) Enable Chromedriver’s performance logging (default false)
Timeout in seconds used to wait for a device to become ready after booting
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.
Thanks for reading the post and watching the video !!!
Please leave your comments and let me know if there is anything I should update in this post.