Mobile Quality Challenges At Zalando
Download as PPTX, PDF1 like588 views
This document discusses quality challenges for mobile apps at Zalando. It provides details on testing approaches for their iOS, Android, and mobile website offerings. For iOS, it describes their Objective-C/Swift project, unit and integration testing, continuous integration, and post-release monitoring. Android testing focuses on Espresso UI tests on emulators and manual device testing. The mobile website is tested manually on devices and browsers as well as with automated Appium tests locally and on Saucelabs. Ensuring quality requires a multi-stage process including test automation, code reviews, and monitoring crash reports and user reviews.
Mobile Quality Challenges At Zalando
- 1. Mobile Quality Challenges At Zalando Dmitry Bespalov <dmitry.bespalov@zalando.de> Hendrik Seffler <hendrik.seffler@zalando.de>
- 4. Zalando mobile apps facts
- 5. Zalandos mobile offerings Developed by dedicated team Developed across multiple teams Developed by dedicated team iOS Android Mobile site
- 6. Team setup Each team is autonomous and responsible for its deliverables. Slightly different development and testing approaches everywhere
- 7. Mobile Testing Pyramid Source: http://www.ministryoftesting.com/2014/10/mobile-test-pyramid/
- 8. iOS Dmitry Bespalov • iOS Engineer
- 10. ● Objective-C & Swift project ● 7 developers ● Giflow workflow Setup
- 11. Testing
- 12. ● Unit tests (TDD) ● End to end integration tests ● Continuous integration ○ Jenkins ○ Xcode server ○ TravisCI ● Testing of iOS beta SDKs Testing
- 13. ● Code review ● Bug bashing ● Post-release monitoring ○ Fabric ○ AppStore reviews Safety nets
- 14. ● Ensuring quality is a multi-staged process ● Test automation is a key component ● Code reviews and bug bashing before release ● Crashes and app store reviews iOS Summary
- 15. Android espresso - “a fun little Android UI test API” ● few unit tests ● espresso based UI-tests (run on emulators) ● manual testing on real devices
- 16. Zalandos mobile website For users that do not have the app installed Targeted from Google searches Initially developed by a dedicated team We faced several challenges
- 17. Quality by organisational changes Responsibility moved to multiple teams Each team has to think about mobile Establish “mobile first” mindset
- 18. Testing the mSite ● Manual testing ○ browser developer tools ○ physical devices ○ saucelabs ● Automated ○ Appium ■ local ■ saucelabs
- 19. Conclusion ● Quality is a team responsibility ● Automated testing plays important role in ensuring quality ● Use all kind of testing: unit tests, end-to- end, manual ● Implement development best practices to have safety nets