How we took Appium to 11 platforms
summary
Built a custom Appium Driver for 11 platforms that maps the engine's scene tree to XML, adds a TCP socket server + XML scene tree automation layer, and proxies system commands to platform drivers so installs and launches work. Tests reuse the same selectors across iOS, Android, tvOS, Tizen, WebOS, PS4, Xbox, macOS, Windows and Linux and often pass on first run; solved missed-clicks with multi-target checks, added an attribute filter for brittle locators, and emulate remotes via sendKeys-as-remote to navigate TV apps.
AI-written summary · about
chapters (37)
- 0:00Introduction
- 1:29Table of Contents
- 1:58UI Key
- 2:32Solution
- 3:00Deployment
- 3:37Meeting customers
- 4:08Running Appium
- 4:42Open Source
- 5:42Automation
- 7:02UI Engine
- 8:18Proof of Concept
- 8:36Minimum Viable Product
- 9:54Mixed cliques
- 11:01Unique locators
- 12:00Resolving issues
- 12:38Customer support
- 13:01Socket server
- 14:07Allterrain D
- 15:10Tizen
- 16:02Navigation Keys
- 17:54React Native
- 19:41Next steps
- 21:06Recap
- 22:30Resources
- 23:24Platform agnostic
- 24:28Demo
- 29:46OS X Connector
- 33:54Conclusion
- 34:54Launching the App
- 36:54Engine vs Driver
- 37:54TV Remote
- 38:54Android KitKat
- 40:54Learning curve
- 41:54Making changes
- 42:54Documentation
- 43:54Progress
- 44:54Time relation
related talks
57mAppium: Automation for Apps
46m6 Years of Appium
39mAppium: An Open Source Software Success Story
30mAppium For Couch Potatoes
52mBuilding an Advanced Automation Solution Based on Appium
46mMy Journey with Appium
19mBuilding an appium driver to automate custom built hardware
22mAutomating the difficult, real-world, multi-user scenarios