Starling Bank Londroid




Starling Bank Londroid

21 February 2018


Added 01-Jan-1970

The February Londroid will be hosted at Starling Bank.

IMPORTANT REGISTRATION INFORMATION: You will need to register on Eventbrite to gain entrance to this FREE event. Registration will open on the 5th February at 10am & the link will be found HERE:

These extra steps of registration have been implemented to assist the security measures in place, to enter London office buildings. We appreciate you taking the extra time to do this.

Evening schedule

6:00 Arrival

6:45 Welcome to Londroid

6:50 Talk One

7:20 Q&A

7:30 BREAK

7:40 Talk two

8:10 Q&A

8:20 Social

9:00 Event closes


Talk One: How to make your unit tests Spektacular using Kotlin and Spek

A dive into the Spek BDD testing framework written in Kotlin. It's the cool kid on the block when it comes to unit testing your Kotlin and Java code. We'll be looking at how Spek improves upon traditional JUnit tests, what other benefits it brings and best practices that have emerged from our experience with it.
Attend this talk if you want to make your unit test code more structured, easier to read and grok when your unit tests start failing.
My talk is motivated by the desire to share best practices. JUnit 4 has been around for almost 12 years and I have a lot of respect for it and think it's a robust framework. However, while Java and Kotlin have advanced JVM development by leaps and bounds, JUnit stayed pretty much the same over the years.

Speaker - Mikołaj Leszczyński

Android Software Architect at Babylon health, previously at Just Eat. Still searching for mobile architecture nirvana. Massive fan of reactive patterns and Kotlin. Has been recently dabbling in some functional programming concepts. Looking forward to teaching his daughter programming once she's old enough. Boardgamer and motorcyclist. Twitter: @TheAngroid


Talk Two: 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, do 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 and


Follow us: @londroid (

Email us: 📧

Join Londroid Slack here (