Recommended
More Related Content
What's hot
What's hot (20)
Similar to MAD-Lab - Mobile Automation Device Lab
Similar to MAD-Lab - Mobile Automation Device Lab (20)
Recently uploaded
Recently uploaded (20)
MAD-Lab - Mobile Automation Device Lab
- 2. Who are we? Priyank Shah Sr. QA Engineer @Vuclip Pvt. Ltd @priyank217 Lavanya Mohan QA Engineer @Vuclip Pvt. Ltd. @LavanyaMohan210
- 3. What are your expectations from this session?
- 4. Some context of the App Under Test
- 5. OTT app with dynamic content
- 6. Search
- 7. Download
- 8. Ads
- 9. Offers
- 10. Other Details ● Android, iOS and Desktop / Web platforms ● Different regions ● Large number of unique device-OS combinations
- 11. What does it mean from testing perspective?
- 12. ● Different devices / OS combinations ● Different carriers and network conditions ● Testing new features and ensuring the existing features work as before ● Give visibility to business about overall quality of the product
- 14. Experiments ● Devices → Some devices are not automation friendly ● Emulators → App not supported ● Cloud based solutions → App not available due to geo restriction Carrier network simulation Device options
- 16. ● Cover business critical user journeys ● Aligned with continuous integration eco systems ● Generated meaningful and rich reporting
- 17. Automation Technical Stack ● Cucumber-jvm → To define business rules ● Appium → To allow integration with Android/iOS ● Gradle/Groovy → As a build tool & scripting language ● TTA → For test trend and failure analysis
- 19. Test triggers and other details E2E Functional Tests App Build API Deployment Automation Code Change
- 20. Node and Pipeline Jenkins Node (appium server) Jenkins E2E Job (./gradlew e2e) Runs on Feature 1 Feature 2
- 21. Stages
- 22. Rich Reports
- 23. Reports
- 24. Analytics automation - At source
- 25. TTA
- 26. Few things done
- 27. Distribution of tests and parallel execution
- 28. ADB Utils
- 29. MAD-Lab
- 31. With few devices
- 32. Now - Better managed And space for more...
- 34. Demo
- 35. References ● Blog by Anand Bagmar: https://essenceoftesting.blogspot.com/sear ch/label/madlab ● Test Code Infra: https://github.com/anandbagmar/cucumbe r-jvm-appium-infra ● TTA Code: https://github.com/anandbagmar/tta
- 36. Thank You Priyank Shah @priyank217 Lavanya Mohan @LavanyaMohan210
Editor's Notes
- Priyank
- Lavanya
- Lavanya asks question to Priyank
- Priyank full slide
- If we have to test all features on wide variety of devices manually and also repeat the tests before every release, manual option is not feasible right? So, we definitely need automation. --------- When we start automation, we need to select which devices to run the tests on. I guess running tests on the devices that are “most used” by our consumers will give us maximum value from the tests. So, we need to first identify the devices that are most used by our consumers. In the products that you are working on, have any of you tried to find the devices that your consumers use the most? --------- Priyank explains how we selected our devices
- Lavanya mentions that we have build in-house device lab. In the journey, we’ve done experiments, failed fast and learnt. We’d like to share that. We started to first run tests on emulators → explain why it didn’t work Lavanya says next logical thing would be to run tests on cloud based solution. Asks Priyank why it didn’t work. Priyank explains cloud based solution doesn’t work. Priyank mentions that “Hence, we build our own in-house device Lab” Lavanya talks about devices in MAD-Lab
- Priyank full slide → Ask question about what are the critical journeys
- Priyank full slide
- Lavanya
- Lavanya
- Lavanya
- Lavanya
- Lavanya
- Lavanya
- Lavanya → execution time → comparing test runs and figuring flaky tests
- Lavanya full slide → device utilization efficiently → server management → infra code part of groovy script → adb utils → adb connection, wifi → analytics at source → performance data → framework supports ios and android
- Lavanya full slide → device utilization efficiently → server management → infra code part of groovy script → adb utils → adb connection, wifi → analytics at source → performance data → framework supports ios and android