Mobile Automation with Appium
Download as PPTX, PDF2 likes3,415 views
The document discusses challenges in mobile automation testing and provides an overview of Appium as a tool for mobile test automation. It covers Appium architecture, requirements, capabilities, and tips for scaling mobile tests. Advanced Appium actions like horizontal and vertical swiping and chained locators are mentioned. The document also discusses visual testing, accessibility testing, and performance testing for mobile apps using Appium.
Mobile Automation with Appium
- 1. Mobile Automation with Appium Manoj Kumar
- 2. About Me âOpen Source Enthusiast (Selenium, ngWebdriver, Serenity, Protractor et..) âAuthor assertselenium.com & official documentation of Selenium âOrganizer & Program Chair seleniumconf.com âMember of Project Leadership committee - Selenium âAccessibility enthusiast âI work at Applitools AI-POWERED VISUAL TESTING AND MONITORING
- 3. Todayâs Session âChallenges of Mobile Automated testing âGetting started with Automated Mobile Testing -Appium âAdvanced features and unique capabilities âScaling your Appium tests âState of Mobile Automation testing tools â& More
- 4. TOO MANY DEVICES + BROWSER COMBINATIONS TO TEST TEST MATRIX IS TOO BIG TO COVER MANUALLY
- 5. RELEASE CYCLES KEEP GETTING SHORTER CI-CD PROCESSES DEMAND AUTOMATION AND ZERO MANUAL BOTTLENECKS
- 6. Automate it!
- 7. Challenges - Mobile Automation âą Validate every OS version your app supports âą Validate every locale your app supports âą Validate different device manufacturers âą Validate performance of your mobile apps âą Simulator vs Real Device differences
- 9. Be Honest
- 11. Appium
- 12. Appium Philosophy âą Test the Same app you submit to the marketplace âą Write automated tests in any language / framework âą An open-source mobile automation framework âą Come up With your own driver implementation
- 13. Appium âą Appium is a HTTP server that creates and handles WebDriver session through Mobile JSON WP
- 14. Appium Architecture âą Similar to WebDriver Server âą A Client-Server architecture âą Server - Node Js âą Client - your Automated Scripts âą Receive request from Client > Executes commands on devices/emulators > A HTTP response is responded
- 15. Appium Architecture âą When you download Appium Desktop or install via npm - youâre just downloading or setting up the Server part of Appium âą When you write an automated Appium Script and execute it, a HTTP request in JSON format is sent to Server âą Appium sends the commands to iOS and Android platform in a way that it understands via bootstrap- which acts as a Unix/TCP server
- 16. Appium in a Nutshell
- 17. Appium Landscape
- 18. Source: Jonathan Lipps- CloudGrey
- 19. Appium Requirements âą Appium via npm server âą Driver Specific Setup âą XCUITest Driver - iOS âą Mac, Xcode > 7, XCUITest library âą UiAutomator2 Driver( EspressoDriver at it Beta Stage) - Android âą Java 7, Android SDK âą Windows Driver - Win Desktop Apps âą Mac Driver - Mac Desktop Apps
- 20. Appium Server
- 23. Appium Inspector
- 24. Advanced Appium Actions Name Some please?
- 25. Horizontal Swiping Thanks - Srinivasan & Sai
- 26. Vertical Swiping
- 27. Vertical Swiping Thanks - Srinivasan & Sai
- 28. Chained Locators
- 29. Any Possible Thanks - Srinivasan & Sai
- 30. Tips & Tricks âą No XPath âą Use Predicates in iOS âą Appium is slow âą Stability over speed âą No Docs
- 31. Performance Testing for Mobile apps âą Mobile apps are usually run in a very constrained environment âą Mobile apps have the potential to create bad user experience not only from UI perspective but also by jamming CPU or memory and shown as a âbattery draining appâ
- 32. âą At least with Android âą dumpsys is a tool that runs on Android devices and provides information about services and can be used wth Android Debug Bridge âą Allow you to check how your application affects the overall device through CPU, RAM, Battery, storage stats List<List<Object>> data = driver.getPerformanceData("io.appium.android.apis", "memoryinfo", 10); Performance Testing with Appium
- 33. Visual Testing for mobile Apps âą Validate if your app looks same on different screen sizes, different manufacturers âą How will your app layout or structure looks when used in different language which has long strings like Deutsch âą Consider testing in Landscape mode
- 34. AI-POWERED VISUAL TESTING AND MONITORING
- 35. Accessibility Testing for Mobile Apps âą All activatable elements should be focusable âą The user flow on the screen should be from top to bottom and left to right. The flow throughout the app should be intuitive.
- 36. Accessibility testing with Espresso âą Accessibility Test framework from Google - Plugged into any Java framework âą Espresso: import android.support.test.espresso.contrib.AccessibilityChecks; @RunWith(AndroidJUnit4.class) @LargeTest public class AccessibilityChecksIntegrationTest { @BeforeClass public static void enableAccessibilityChecks() { AccessibilityChecks.enable(); } }
- 38. Scaling Mobile Automation âą Dockerize Appium Tests - Easy Parallel tests âą Docker based Setup âą https://github.com/butomo1989/docker-android âą https://github.com/appium/appium-docker-android âą No more worry about requirements âą Comes pre-built in a docker image âą Build an Image and execute it!
- 39. Scaling Mobile Automation âą Appium Test Distribution âą Appium Device Manager âą Remote Appium Manager
- 40. Video Demo
Editor's Notes
- #5: Unlike 5 or 10 years ago in todays world, when testing a web or mobile app - whether native or responsive, itâs important to be able to test on all devices and browsers. The problem is, there are simply too many device and browser combinations. Chrome, Firefox, IE, Safari, each one has multiple versions that customers may be using, on different devices (PC, MAC, Mobile Devices, Smart watches) Running on different operating systems (Windows, Linux, IOS, Android etc.) and in different screen resolutions according to the device. In some cases the application under test may also have responsive design to optimize the layout according to the viewable portion of the screen. In these cases we also need to check the app across the different layouts. While there are tools that let you test on a wide variety of devices, there is no automated testing tool that can see that the app looks and acts right on all devices. So someone still manually goes through each and every device, to ensure that everything is displaying properly. This causes major bottlenecks which adds cost to the dev process.
- #6: On top of that we also know that release cycle are keep getting shorter and shorter. Many organisations already have CI in place and some already has full CD. It simply means that everything must be automated has we have zero time for manual bottle necks. So, we have more and more things that we need to cover and less and less time to do it.