Understanding Appium Desired Capabilities and Session
Karthik kk
In this post we will start our discussion on Appium Session and Appium desired capabilities
Appium sessions
In Appium all the commands (client commands) are executed in the context of a session.
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 desired capabilities object.
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
(Chrome and webview only) Enable Chromedriver’s performance logging (default false)
true, false
androidDeviceReadyTimeout
Timeout in seconds used to wait for a device to become ready after booting
e.g., 30
androidDeviceSocket
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.
e.g., chrome_devtools_remote
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.
Thanks,
Karthik KK