Workshop: Mastering Appium 3: Architecture, Gestures & Beyond
summary
Appium 3 ships as a modular, pluginable server (released two days before the workshop) that requires Node >=20.19 and npm >=10, moves inspector into a plugin that can run in the browser, and keeps client code working via official bindings that fallback where needed. Plugins can override findElement or listen via Bidi for ADB logs or system popups. Gestures use the W3C Actions API (pointerDown/pause/pointerMove/pointerUp); an MCP code generator produces working Java scroll sequences that ran in the demo.
AI-written summary · about
chapters (18)
- 0:00Mastering Appium 3 intro
- 1:49Appium 3 architecture
- 6:02Appium client-server & drivers
- 10:55Appium plugins deep dive
- 20:24Appium 3 key updates
- 27:50Migrating to Appium 3
- 38:17Appium Inspector plugin
- 40:25Appium 3 server flags
- 44:25Migration concerns and deprecated commands
- 49:47Demo project setup
- 53:23Touch Actions to W3C
- 1:00:08Gesture code with MCP
- 1:13:03WebDriver IO & Java updates
- 1:18:46Concurrent sessions & isolation
- 1:23:06Appium for IoT & 5G
- 1:25:10Appium in CI/CD
- 1:27:37AI-assisted script maintenance
- 1:29:45Q&A
related talks
32mAppium Automation for iOS and Android
15mIntroduction to #Appium 2.0 | How to Update to Appium 2
15mAutomate Any App with Appium #AAAA
15mChoose a Mobile Test Automation Framework That Suits Your Team
38mBuilding Your Own Native App Visual Testing Module with Appium
39mUsing Appium for Unity games and apps
33mHow React Native, Appium and me made each other shine!
30mTesting & React Native"Lessons from the Battlefield"