Evolution of mobile test automation at Badoo: from 0 to 45 hours of tests

Challenges in mobile test automation (Android, iOS and mobile web) are quite different from desktop web. Applications are developed with different technologies on different languages and different platforms. You need a strategy while picking the tools for mobile test automation. It is important to understand what you want to achieve with it and how to show the value to your stakeholders.

Having automation tests doesn't mean anything by itself. Speed and stability of your tests are necessary to build the trust between the developers and QA. While we want to see a pyramid structure in testing — unit tests, integration tests, etc. — end-to-end tests are not merely the pointy bit at the top, but are the bridge between client and server pyramids.

Badoo delivers Android and iOS applications once in a week and mobile web twice per day. While the product is continuously pushing for the features and teams got scaled over the last two years, how do we start working with developers and manual QA and keep being a part of its delivery process?