The document discusses the importance of mobile app testing and some of the challenges involved. It notes that 48% of users won't use an app again after encountering issues. Various testing approaches like manual testing and automation are presented, and it is argued that automation is key for high test coverage and reducing time to market. Challenges like device, OS, and screen size fragmentation are also covered.

2. About Me
TestObject GmbH
Co-Founder I Sales
Mobile Quality Crew’s
Co-Founder I Organizer
Contact:
@testobject I timo@testobject

3. Session
1) Mobile app testing: Why it is important
2) Challenges
3) Different testing approaches
4) Automation as key factor for success

4. Familiar?
48 % of users won‘t use an
app again after encountering a
major issue!
Source: Compuware Global Study Mobile Apps 2013

5. Better Find Bugs Before Users Do

6. Bad Quality = Less Revenue
Quality
Ratings
Downloads
Revenue

7. App Testing Challenges

8. Device Fragmentation
http://opensignal.com/reports/2015/08/android-fragmentation/

9. OS Fragmentation
http://opensignal.com/reports/2015/08/android-fragmentation/

10. Screen Size Fragmentation
http://opensignal.com/reports/2015/08/android-fragmentation/
Android iOS

11. ... More Challenges
§ Mobile means your users are not in a
protected environment
§ Network (Wifi, 3G, GPRS ...)
§ Sensors, Bluetooth ...

12. Learnings
§ Your users are not very patient
§ Quality has direct impact on apps‘
success
§ Challenges: Fragmentation and mobile
use of apps
§ Implication: Mobile QA is a central part
of development

13. There must
be an easy
solution to
handle
this ?!

14. ...nope!

15. What Do I Have to Test?
§ What to test:
§ Usability
§ Functionality
§ Performance
§ Edge Cases
§ Approx. 50 use cases (per platform)
§ Approx. minimum 20 target devices

16. Testing Framework
Development QA Production
Unit Tests
Functional Tests
Usability
Sanity
Monitoring
Automation
Manual Edge Cases
Checkups

17. Manual Approaches
§ Checkups, Usability, Edge Cases, Performance
§ Pros: You can test the actual user behavior
§ Cons: Time consuming, inefficient

18. Continuous Delivery = Continuous Testing
Build
Test
Deploy
Enhance

19. UI Automation Approaches
§ Regression, End-to-end, Integration
§ Pro: High test coverage, scalable, time-to-market,
releases resources for manual testing
§ Con: Initial investment, requires technical know-
how, maintaining of scripts, no edge cases

20. Automated Testing
ROI
Investment
Test Cycles
Resources

21. UI Automation Components
§ CI & Build: Jenkins, Bamboo, Travis CI, Gradle, Ant,
Maven
§ Scripting Tool: Proprietary or Open Source Tools
§ Infrastructure: e.g. Spoon, Selenium Grid,
SauceLabs, TestObject ...

22. UI Automation Frameworks
iOS Android Web Language
Calabash
x x - Ruby
Robotium
- x - Java
Espresso
- x - Java
Appium
x x x
Java, JavaScript, Python,
Ruby ...

24. Code Example Appium

25. Example Test Execution

26. Learnings
§ Quality is crucial but mobile QA is
complex
§ Different automation and manual
testing approaches are required
§ For decent test coverage and time-to-
market UI test automation is key

27. Thank you!