Last updated: 8 months ago
Mobile DevOps is a practice of bringing the different disciplines involved in developing, testing, releasing, and operating apps into being functional inside organizations or by a team that works closely together. The team is able to continuously deliver their apps based on continuous feedback and iteration. There are different practices, habits and different flavors of adopted company cultures that set the behavior for an actual process and daily doing.
Mobile DevOps and CI/CD pipelines help us to deliver our apps faster than before with great quality, they help us in running our test automation scripts on different stages (every pull request and nightly build) and help us in releasing our apps automatically to our QA engineers, product managers, and our customers.
In this session, I will tell our story behind our Mobile CI/CD and why our team at Delivery Hero adopted native test frameworks for mobile testing. Since using Espresso and XCUITest is still relatively uncommon for large apps and there are various unique challenges, I will share the Delivery Hero team’s experiences, including:
We developed this story over the last 2 years, and I'm sure it will be useful for everyone related to mobile development to learn from our ideas.
Can you expend a little bit on what you mean by Mobile DevOps?
I'd be also super interested in your experience running a lot of XCUITest and Espresso tests. What's not working? What did you do to address the problems in each framework?
Also, is this talk about both iOS and Android? It seems like a lot to cover in 35-40 minutes without being too shallow.
Thank you for the proposal!
I updated the proposal, yes it will be for both iOS and Android
I would suggest hiding the company name from the proposal (at least until it’s chosen) as per UIKonf CfP’s proposal guidelines.
I updated itLog in to comment