Mobile Testing Challenges at Zalando Tech
-
Upload
zalando-tech -
Category
Data & Analytics
-
view
321 -
download
0
Transcript of Mobile Testing Challenges at Zalando Tech
Mobile Quality Challenges At Zalando
Dmitry Bespalov <[email protected]>Hendrik Seffler <[email protected]>
Zalandos mobile offerings
Developed by dedicated team
Developed across multiple teams
Developed by dedicated team
iOS Android Mobile site
Team setup
Each team is autonomous and responsible for its deliverables.Slightly different development and testing approaches everywhere
● Unit tests (TDD)● End to end integration tests● Continuous integration
○ Jenkins○ Xcode server○ TravisCI
● Testing of iOS beta SDKs
Testing
● 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
Android
espresso - “a fun little Android UI test API”
● few unit tests● espresso based UI-tests (run on emulators)● manual testing on real devices
Zalandos mobile website
For users that do not have the app installedTargeted from Google searches
Initially developed by a dedicated teamWe faced several challenges
Quality by organisational changes
Responsibility moved to multiple teamsEach team has to think about mobile
Establish “mobile first” mindset
Testing the mSite
● Manual testing○ browser developer tools○ physical devices○ saucelabs
● Automated○ Appium
■ local■ saucelabs