Android DevOps: Espresso on Genymotion in AWS

Talk one: Android DevOps: Espresso on Genymotion in AWS

How do you create a mobile-only bank account that customers trust enough to deposit money in? The mobile application needs to be high quality. After evaluating and comparing what other companies, small and big, use to test their android application and the available technologies (device farms, hypervisors...), we picked Genymotion-on-Demand and built a continuous integration system in the AWS cloud. The cost and coverage of running tens of thousands of Espresso tests every day are measured. We have fragmentation of OS versions and screen sizes. Tests are sharded to reduce build time. Videos of tests are recorded. JUnit test reports are generated. We had to adapt to open source libraries breaking because of new versions of the Android toolchain. This is a multi-technology stack using Android, Bash, Gradle, Cloud Formation, Teamcity, Slack, C++, Python, Groovy, Artifactory... This is about sharing the journey and what we learned along the way, from building internal buy-in to providing feedback to Genymotion itself and the many technical things that broke along the way. We are using this system and plan to expand it with Appium tests for application upgrade and stress testing.

Speaker: Michael Aubert

10 years ago, Michael Aubert was tricked into writing a programming book. With that endeavor now thankfully completely obsolete, he's trying to bring more competition to a banking industry that sorely needs it by contributing what he can to the Starling Bank Android application. He still hasn't automated @PandoUnlocks.

@michaelaubertfr

Тэги:

#Android

Скачать видео