Download to read offline
![Fragile locator example
(//div[contains(@title,’title’)]//p[text()="Some Text 1”]/following-sibling::span[5]/parent/)[position() < 6]](https://image.slidesharecdn.com/scalingmobileautomation-180529173451/75/Scaling-mobile-automation-by-Pavel-Kulagin-17-2048.jpg)
Uploaded byBadoo
Scaling mobile automation by Pavel Kulagin
Pavel Kulagin discussed scaling mobile automation at Badoo. He covered first implementing tests and problems encountered, increasing test amounts while maintaining a proper test pyramid with more integration and unit tests than UI tests. Kulagin emphasized helping rather than obstructing others and calculating time saved. Tips included treating automation code like production, supporting parallelization, smart test runs, documentation and easy setup. Mythbusting dispelled ideas that 100% functionality can be automated or all tests require real devices. The key is decreasing flakiness, increasing speed, and creating an easy to use tool while supporting developers and QA.
More Related Content
Similar to Scaling mobile automation by Pavel Kulagin
Scaling mobile automation by Pavel Kulagin
- 1. Pavel Kulagin Scaling MobileAutomation …probably not just mobile in the end…
- 2. Pavel Kulagin Hello, myname is github.com/badoo badootech.badoo.com github.com/kuwizard Professional focus: QA & mobile since 2009 Background: big Russian companies - Yandex and OK Current role: scaling automation at Badoo for the last 2.5 years
- 3. About 350m Messages per day 380m Registeredusers worldwide 60m Monthly active users 300k New daily sign ups
- 4. Agenda First tests andfirst problems Increasing amount of tests Company culture Tips & Tricks Mythbusting
- 5.
- 6. We need teststo provide confidence that the software being released to production works as intended “ ” — Sathish Gogineni, Badoo mobile automation team lead
- 8. Continuous Integration • Thefirst few tests are green • It takes only 10 minutes to run all of the tests • We’ve even included tests for the automated deployment pipeline!
- 9.
- 10.
- 11.
- 12.
- 13.
- 14. Flaky tests • FlakyApp Wait for specific event Backdoors • Wait/sleeps • User is not eligible
- 15.
- 16. Flaky tests • FragileLocators • Flaky App Wait for specific event Backdoors Use server API to get users • Wait/sleeps • User is not eligible
- 17. Fragile locator example (//div[contains(@title,’title’)]//p[text()="SomeText 1”]/following-sibling::span[5]/parent/)[position() < 6]
- 18. Flaky tests • Iknow this test fails usually • Fragile Locators Work with/as a developer Debug and fix it! • Flaky App Wait for specific event Backdoors Use server API to get users • Wait/sleeps • User is not eligible
- 19. • Slow responsefrom server Slow tests • Something else • Tests do some repetitive actions • Slow infrastructure Mock it Backdoors again! 😥 Analyse every test step-by-step and think bigger
- 20.
- 21. Build Internal App Store QA Release Fixes Happy releasepipeline Mutes Auto Tests Auto Tests Auto Tests
- 22. First tests andfirst problems Increasing amount of tests Company culture Tips & Tricks Mythbusting Agenda
- 24. Scaling is… NOT about increasingamount of UI tests!
- 25.
- 26.
- 27.
- 28.
- 29. Agenda First tests andfirst problems Increasing amount of tests Company culture Tips & Tricks Mythbusting
- 30.
- 31. Company culture • Help,don’t obstruct • Move away from the “Devs VS QA” paradigm
- 32. • Help, don’tobstruct • Move away from the “Devs VS QA” paradigm Company culture • Calculate the time you saved for others
- 33. Calculations example Before After x 3days Total: 12 person-days x 2 days = 6 person-days x 0.5 days = 0.5 person-days Total: 6.5 person-days
- 34. • Help, don’tobstruct • Move away from the “Devs VS QA” paradigm • Calculate the time you saved for others • Use company resources (people) • Involve others to contribute • Make it easy to procure hardware Company culture • Gather feedback for your tool and make it convenient to use
- 35. Fast-forward to thefuture
- 36. Agenda First tests andfirst problems Increasing amount of tests Company culture Tips & Tricks Mythbusting
- 37. • Treat automationcode as production one • Support parallelisation (Selenium Grid?) • Smartify your test runs • Write documentation • Make first start as easy as possible Tips & Tricks
- 38. Automation framework installationinstructions Before After • Install Docker • Run docker-compose run <options> test <tests>
- 39. Agenda First tests andfirst problems Increasing amount of tests Company culture Tips & Tricks Mythbusting
- 40.
- 41. Mythbusting • You canautomate 100% of functionality (and dismiss QAs) • You should test everything on real devices only
- 43. Mythbusting • We needto cover every possible environment • Every test should be atomic - check one thing only • You can automate 100% of functionality (and dismiss QAs) • You should test everything on real devices only
- 44. Summary • Decrease flakiness •Increase speed • Make easy-to-use tool • Keep the test pyramid in mind • Support developers & QA
- 45.