How To Write a Symphony of Automation With Appium by Dan Cuellar sauce con18
Download as PPTX, PDF1 like83 views
The document discusses Dan Cuellar's creation of Appium, motivated by the need for effective mobile automation tools akin to Selenium for web applications. It explores the generalizability of automation across platforms and the importance of standardized protocols like WebDriver for system compatibility and user engagement. Future advancements in automation are proposed through a common framework that enhances test adaptability across various devices and operating systems.
How To Write a Symphony of Automation With Appium by Dan Cuellar sauce con18
- 1. HOW TO WRITE A SYMPHONY OF DAN CUELLAR
- 2. ABOUT THE SPEAKER DAN CUELLAR ▸Creator of Appium ▸Experienced Software Engineering Manager ▸BS in Computer Science from Carnegie Mellon University
- 3. THE INCEPTION OF APPIUM INSPIRATION ▸Selenium is a great tool for automating web applications ▸There were no good tools for automating mobile applications ▸Why can’t I automate mobile applications like I automate web applications with Selenium
- 4. THE INCEPTION OF APPIUM LEARNINGS ▸Automation is very generalizable across multiple platforms/devices ▸Surprisingly little needed to be changed in the WebDriver protocol to support iOS and Android ▸I should have asked, “Why can’t we automate everything like I automate web applications with Selenium?” ▸Basing Appium on a widely accepted standard (WebDriver) facilitating easy adoption and the growth of the Appium user community
- 5. THE INCEPTION OF APPIUM WHAT’S NEXT? ▸How can we start talking about automation at a more general level such that we can use one framework to automate anything? ▸What do we stand to gain from a common automation standard? ▸How do we get device and operating system vendors on- board so that this will all work out of the box? ▸No more automation frameworks
- 6. MUSIC THE ULTIMATE PLUG AND PLAY
- 7. AN ANALOGY MUSIC NOTATION ▸ The composer doesn’t know how to play every instrument in the orchestra, but can write for all of them ▸ The musicians control the instruments based on common notation ▸ Capabilities constrain which instruments play which parts
- 8. AN ANALOGY THE WEBDRIVER PROTOCOL FOR COMPOSERS ▸Instrument Capabilities ▸Name: Piano ▸Range: A1 to C8 ▸Polyphony: true ▸Pitch Bends: false ▸Sustain Control: true
- 9. AN ANALOGY IT GETS MORE COMPLICATED ▸A Guitar is polyphonic but… ▸Only 6 notes at a time ▸Each string can produce 1 of 25-ish notes ▸Some fingering would be impossible for a human ▸A Piano has sustain, but in several configurations ▸It can sustain only certain notes, but only in certain configurations
- 10. AN ANALOGY REPRESENTING COMPLEXITY ▸Capabilities as functions to cover complex states? ▸Each guitar string as its own input? ▸Each hand/foot/finger as an input to the piano?
- 11. GENERIC AUTOMATION A HIGHER LEVEL OF ABSTRACTION
- 12. GENERIC AUTOMATION QUIRKS OF APPIUM BECAUSE IT’S BASED ON WEBDRIVER For a first pass as to what abstractions need to be made, you can look at Appium’s methods and uncover it’s web-based automation base: ▸element.click() ▸getPageSource() ▸browser
- 13. GENERIC AUTOMATION OBVIOUS ABSTRACTIONS ▸.click() -> .press()? ▸browser -> device ▸getPageSource -> getUIHierachy()
- 14. GENERIC AUTOMATION HIGHER-LEVEL ABSTRACTIONS ▸Devices have Operating Systems ▸Operating Systems have Applications, Inputs, and Outputs ▸Applications have user interfaces ▸User interfaces have elements ▸Elements are manipulated via inputs to affect outputs
- 15. GENERIC AUTOMATION DEVICE LEVEL ▸Device Capabilities ▸Hardware Buttons (Power, Volume Up/Down) ▸Plug / Unplug Cable
- 16. GENERIC AUTOMATION OPERATING SYSTEM LEVEL ▸Install Application ▸Launch Application ▸Is Application Installed ▸Set Date/Time, Language, etc. ▸Get Input / Output Interfaces
- 17. GENERIC AUTOMATION APPLICATION LEVEL ▸Application Settings ▸Get User Interface Hierarchy ▸Interface with User Interface Element (using associated inputs / outputs)
- 18. GENERIC AUTOMATION INPUTS / OUTPUTS ▸Press / Gesture at coordinates on Touch Interface ▸Get Screenshot of Graphical Interface ▸Press Mouse Button ▸Type on Keyboard ▸Speak into Microphone
- 19. GENERIC AUTOMATION AN EXAMPLE ▸An HP Pavilion is a device ▸The HP Pavilion has the Windows Operating System ▸Windows has the Firefox Application and a mouse, a display, and a keyboard ▸The Firefox application has a user interface (web-based interface)
- 20. GENERIC AUTOMATION ANOTHER EXAMPLE ▸An iPhone is a device ▸An iPhone has the iOS operating system ▸The iOS Operating System has the Spotify application, a touch input, an audio output, and a graphical output ▸Spotify has a user interface
- 21. GENERIC AUTOMATION EXTENSIONS ▸Bluetooth headphones are an additional output / input (if there are controls) ▸Should a wearable be represented as an additional input or output or a separate device?
- 23. WHY ABSTRACT? TEST LEVELS ▸Tests can be written at any / all of these levels ▸If a test is written at the application level, then in theory it could work on any operating system (provided the behavior matches) ▸If a test is written at OS level then it could be run on any device that supports that OS ▸Tests are inspectable and self-documenting
- 24. WHY ABSTRACT? PLUG & PLAY ▸If Device and OS vendors are onboard you can add automate new technologies without having to learn a new framework ▸You can write tests that are future-proof ▸Onus is on the application developer to provide unified paradigms and interfaces to support using multiple device categories
- 25. WHY ABSTRACT? CAPABILITIES ▸By capabilities can I tell where a test can run? ▸Can I add my own domain-specific capabilities to see where my tests can run ▸Capabilities at application level and operating system level, not just the device level
- 26. WHY ABSTRACT? APPLICATION CAPABILITIES EXAMPLE ▸App Capabilities ▸Log in ▸Send a message ▸Read a message
- 27. WHY ABSTRACT? IMAGINE… ▸AOL decides to release a new mobile phone operating system ▸It ships with an automation framework that has binding for generic automation ▸As a tester you can see what inputs, outputs, and applications are available ▸You can now automate
- 28. WHY ABSTRACT? IMAGINE… ▸I want to write a test that works across multiple devices ▸I use app-specific capabilities to expose what my app can do ▸I write automation at the application-level and it can run on many devices
- 29. WHY ABSTRACT? APPLICATION LEVEL AUTOMATION ▸1. Login ▸2. Compose a Message ▸3. Turn off Internet ▸4. Send Message ▸5. Verify Message in Outbox ▸6. Enable Internet Access ▸7. Verify Outbox is Empty
- 30. ADOPTION HOW DO WE GET PEOPLE ON BOARD?
- 31. STARDRIVER EVANGELISM GAINING TRACTION ▸Build more WebDriver compatible automation frameworks ▸Add WebDriver adapters for those that don’t support it ▸KIF ▸Calabash ▸EarlGrey ▸etc. ▸Start writing an automation standard and stop writing frameworks (i.e. replace the freshly minted W3C standard)
- 32. STARDRIVER EVANGELISM GETTING THE WORD OUT ▸Conferences ▸Blogs ▸GitHub ▸Your Own Work