Q & A With The Appium Committee Panel
summary
Nine committers answer how Appium actually got working: early iOS automation uses an AppleScript auth hack and touch‑ID on simulators required AppleScript; the original UIAutomation bridge sends blobs via netcat + UNIX sockets and eval to pass commands; an Android locator solution parses Java UIAutomator strings into reflection calls; Appium Desktop is built and widely adopted; CI runs on Travis with end‑to‑end driver tests and XCUITest jobs that can take ~40 minutes each.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 2:40Worst Appium code
- 8:47Diversity in committers
- 15:09Release test cycle
- 17:05Vendor collaboration
- 19:15Panelist proudest contributions
- 28:56Impact on testing
- 29:18One change for Appium
- 34:112020 conference plans
- 35:09Balancing open-source
- 38:20Closing
related talks
44mQ&A with the Appium Committers [Panel]
57mAppium: Automation for Apps
39mAppium: An Open Source Software Success Story
53mQ&A with the Appium Committers [Panel]
46m6 Years of Appium
52mBuilding an Advanced Automation Solution Based on Appium
23mAppium: Under the Hood of WebDriverAgent
52mAppium 2.0 - State of the Union