Dan Cuellar
1 like1,403 views
This document discusses how Dan Cuellar accidentally created the wildly popular open source mobile testing framework Appium. It describes how Appium works and its philosophy of being inclusive, free, and open source. It provides code examples for setting up tests on iOS and Android. It also outlines how Cuellar grew the project from 0 to over 100,000 users through conferences, forums, and being very inclusive. It discusses challenges like conflict, loss of control, and rewriting the codebase, and looks towards the future of Appium.
![WebElement el = driver.findElement(By.className("UIAButton"));
WebElement el = driver.findElement(By.xpath("//UIATextField[1]"));
WebElement el = driver.findElement(MobileBy.AccessibilityId("Done"));
THE CODE β FINDING ELEMENTS](https://image.slidesharecdn.com/dancuellar-160328125523/85/Dan-Cuellar-13-320.jpg)
Dan Cuellar
- 2. ABOUT THE SPEAKER Dan Cuellar β’ Creator of Appium β’ Head of Software Testing at FOODit β’ Previously at Shazam, Zoosk, and Microsoft β’ BS in Computer Science from Carnegie Mellon
- 9. APPIUM PHILOSOPHY β’ Use standardized and sanctioned APIs and techniques β’ Code in the language of your choice β’ Java, C#, Python, Ruby, Objective-C, node.js, PHP, and more β’ Do not modify the application under test β’ Keep it free and open source
- 13. WebElement el = driver.findElement(By.className("UIAButton")); WebElement el = driver.findElement(By.xpath("//UIATextField[1]")); WebElement el = driver.findElement(MobileBy.AccessibilityId("Done")); THE CODE β FINDING ELEMENTS
- 17. GETTING THE WORD OUT β’ Answered almost every forum question for the 1st year of the project β’ Answered most StackOverflow questions β’ Spoke at any conference that would have us β’ Stated our mission and philosophy β’ Talked to companies that were interested β’ Utilized Twitter and social media
- 18. LOSING CONTROL IS A GOOD SIGN β’ One day a website and twitter account showed up β’ Android support was added β’ The code was ported to another language β’ I lost commit privileges on the repo (briefly) β’ My conference proposal was rejected because, unbeknownst to me, two other people had already submitted Appium talks at the same conference
- 19. SCALABILITY β’ Eventually, you wonβt be able to answer every question β’ Other people will have learned from reading the forums and the community can answer β’ You wonβt be able to test or scrutinize every commit β’ Unit tests are your friend β’ You wonβt know the whatβs on anymore β’ Draft good release note β’ Keep detailed commit messages
- 20. STARTING AN OPEN SOURCE PROJECT THE WRONG WAY β’ Use proprietary technologies β’ Share the code via email β’ Provide no documentation β’ Do not post slides β’ Respond to issues via private communication THE RIGHT WAY β’ Use open technologies β’ Post code on GitHub β’ Write documentation β’ Use Slideshare & YouTube β’ Post responses on forums
- 22. CONFLICT β’ Agreeing to a philosophy and/or mission beforehand is helpful β’ There is no rigid chain of command to resolve disputes β’ Conflict is best kept out in the open β’ This leads to debate which results in better decisions β’ Transparent decision making leads to better end-user understanding β’ Sometimes whoever writes the code make the decision β’ People may have opinions but arenβt willing to code the solution
- 23. WHEN PEACE IS NOT AN OPTION β’ Losing contributors is bad, but not the end of the world β’ Unless they leave the open source community, their work is still shared with everyone β’ Multiple projects doing the same thing isnβt necessarily a bad thing β’ Choice and competition brings about innovation β’ Having options is good for end-users In the end, the most awesome thing will win
- 25. BY THE NUMBERS In the last 3 years β’ Over 3,000 Stars, 2,000 Forks on GitHub β’ Over 150 Contributors and 5,000 commits β’ Over 150,000 downloads of Appium 1.0 β’ Over 3,000 issues closed
- 26. WHATβS NEW IN APPIUM 1.5? β’ Complete rewrite of the entire codebase β’ Continuous Integration and Unit Tests β’ Command line arguments are mostly capabilities now β’ Code of Conduct and Governance
- 27. WHY REWRITE? β’ 3 years of patches and organic growth β’ Many complaints about instability β’ Code was not modular enough β’ Old and confusing ES5 code β’ Callback Hell β’ Poorly Tested
- 28. WHATβS COMING NEXT β’ Windows Phone and Windows 10 application support β’ New GUIs β’ Multiple New iOS Backends β’ Android backend rewrite using UIAutomator 2 β’ Better docs and onboarding material β’ Appium Foundation
- 31. WHY DOES APPIUM SUCCEED? β’ From Day 1, There Was a Clear Philosophy and Vision β’ We try to be as inclusive as possible to foster an active community β’ We support many languages and platforms as β’ Our tool is based on an existing tool people are already familiar with β’ We put a whole lot of work into it β’ We speak at any and every conference that will have us β’ We contribute a lot of our unpaid time into the product
- 32. INCLUSIVENESS
- 33. INCLUSIVENESS
- 34. INCLUSIVENESS
- 35. INCLUSIVENESS
- 37. MORE INFO β’ Website: http://www.appium.io β’ Slack: appium.slack.com β’ Forum: discuss.appium.io β’ GitHub: http://www.github.com/appium/appium