The document discusses the importance of app testing and the challenges involved, such as limited access to real devices and fragmented device markets. It highlights the significance of automated testing on real devices for accurate results and provides insights on what scenarios to test in order to enhance app performance. The presentation also compares various testing frameworks and emphasizes the need for effective testing practices to reduce app uninstalls.

1. Ship Quality Mobile Apps with Speed
#ShipAppsNotBugs
Kalpesh Doshi
Director Product Management,
BrowserStack
Lalit Bihani
Product Manager,
BrowserStack

2. Agenda
SECTION
About BrowserStack
Why App testing?
Why we skim on testing
Best practices
Automate and release faster

3. BrowserStack history

4. 25,000+ Customers

5. Powering the world’s leading open source projects
browserstack.com/open-source

6. Our products

7. Why App Testing? 7Board Meeting |

8. Success of an app is not guaranteed
Apps on Play
Store
2,678,315
Apps without user
rating
Apps >50K
downloads
1,197,584 (45%) 214,616 (8%)

9. 30% users uninstall the app in first 4 weeks

10. How users respond to a poorly tested app
Source: https://www.netsolutions.com/insights/preventing-app-uninstalls-9-ways-for-improving-mobile-app-development/

11. What makes testing difficult
11Board Meeting |

12. Not testing on real devices
● Access to devices is limited
● Setting up a device lab is
expensive
● Testing on Emulator/Simulator is
not reliable

13. Device market is fragmented
● 9500 varieties of devices
● 114 device manufacturers
● 5B+ unique mobile users

14. It’s hard to test like users
14
● User network conditions may
vary
● User may have different
device settings
● User may be accessing from
different locations
● User may be interrupted by
other applications

15. Poor test coverage
15
● Not enough testers
● Project is complicated
● Build arrived late
● Too many regression scenarios
● Release date is due

16. But we want to deliver
awesome apps!
16Board Meeting |

17. 17Board Meeting |
Testing real world scenarios
Testing on real devices
Automate and release faster

18. Why real devices?
● Accurate Results
● Real World Scenarios
● Testing App Performance

19. What devices to test on
● Top used devices
● OS version coverage
● Screen sizes
● Low end devices
● Device manufacturer

20. ● High costs
● Regular maintenance
● Lack of expertise
In-house device lab
VS
Cloud based testing
20

21. Testing real world scenarios
21Board Meeting |
Testing on real devices
Automate and release faster

22. Test your location based features for multiple GPS Geolocation and IP
Geolocation.
What scenarios to test?
Ensure that your app works as expected in poor network conditions.
Verify that UI doesn’t break for different locale settings
Interact with other apps to simulate actual user behavior.

23. 23Board Meeting |
See it in action

24. 24Board Meeting |
Testing real world scenarios
Testing on real devices
Automate and release faster

25. Why Automate?
25
● SPEED
● RELIABILITY

26. What is right framework?
Appium EarlGrey
● Supports iOS and
Android native apps
● Client-Server
architecture as
Selenium
● Supports multiple
languages and
frameworks
● Supports Android
Apps only
● Native framework
developed by Google
● Executes tests much
faster than Appium
● Supports iOS Apps
only
● Native framework
developed by Apple
● Executes tests much
faster than Appium
● Supports iOS Apps
only
● Native framework
developed by Google
for iOS apps
● Executes tests much
faster than Appium

27. Automate real world scenarios

28. Automate real world scenarios

29. How it works?

30. Manual vs Automation
30

31. Do you need help?

32. Questions?
32Board Meeting |