Appium: Under the Hood of WebDriverAgent
summary
WebDriverAgent runs on the device, receives Appium REST calls and transforms REST to XCUITest calls that go to testmanagerd; Appium uses an ibm-ios-device proxy to forward requests to real devices. The talk shows accessibility is the source of the element tree, explains snapshots vs queries, and stresses idling as the root cause of flakiness with idle timeout 15s vs 60s behavior. Also covers auxiliary APIs like MJPEG screen stream and custom extensions.
AI-written summary · about
chapters (13)
- 0:00Start
- 1:04Webdriver Agent
- 3:03Accessibility
- 3:53Accessibility Framework
- 7:35Guidelines
- 8:01How Web Driver Agent Works
- 11:10Appium Based Driver App
- 11:24Appium Ios Device Module
- 14:19Driver Agent Api
- 14:30Management Api
- 17:17Why Your Application Is Not in Idle Mode
- 21:32Questions and Answers
- 22:33Accessibility Ids
related talks
57mAppium: Automation for Apps
01h 23mWorkshop: Debug with Appium MCP
39mAppium: An Open Source Software Success Story
43mUnlocking New Testing Capabilities with Espresso Driver
39mQ & A With The Appium Committee Panel
46m6 Years of Appium
52mBuilding an Advanced Automation Solution Based on Appium
48mBootcamp To Understand Appium Android Internals