Over the past few years, Appium has gained tremendous popularity due to its support of many languages and multi-platform automation possibilities. It is the most popular tool for test automation engineers as of today.
However, there are times when beginner Appium users have a curiosity about how it works under the surface. Some intermediate/advanced users always wonder how to debug their automation code in conjunction with the Appium source code to find out why that element on UI can’t be located or why the click is not working on that custom element.
In this workshop, we will start with the tools that are building a block of higher-level automation frameworks, such as Appium and then we will deep dive into Appium itself.
Agenda:
Evolution till Appium- Brief History and comparison of First Order open source android automation tools (Robotium, UiAutomator, Espresso, UiAutomator2)
- Evolution of higher-order Automation tools like Calabash and Appium.
- Appium as an aggregator of First Order automation tools
Inside Appium- How does Appium work
- Debugging Appium: Using lifecycle of a simple web driver action, we will follow the code path taken by an Appium command and debug/monitor the beautiful journey which will start from client-side Ruby/Java code, JavaScript side of Appium driver finally ending up with Java/Kotlin server inside the android device.
Participants should have laptops with them for hands-on exercises. Coding experience is recommended.Speaker will keep giving the demonstration on his machine. if attendees do not have machine setup done, they can observe and ask questions during the workshop.Installation Requirements:
- Android Studio with Android SDK
- Java
- Chrome Postman
- Node.Js
- Appium
For Java programmers:
https://github.com/rajdeepv/AppiumJavaExampleFor Ruby programmers:
https://github.com/rajdeepv/appium_backdoorsPlease clone
https://github.com/appium/appium-espresso-driver and then run the below command in the root of repo
./gradlew clean assembleAndroidTest
