We’ve known for a long time how to test Java apps and services, but when Android came out, resources were scarce, I’ll even say non-existent. Fortunately, the Android community has grown quite quickly, and we’ve developed various new tools, frameworks, libraries and services to help with app (or library) testing. Many of these utilities were targeted to Java, and have now become compatible with Android — we can now easily run app/library tests on development machines, without having to install the build onto a mobile device.

As time went by, the most popular tools like Mockito, Hamcrest, Espresso and others became our standard for Android app testing, and we’ve adopted them as “defaults”. They have grown over time with many new versions released. We also popularized some new architecture approaches — like MVVM and MVI — and dependency management approaches — like Koin, Kodein and Dagger — all of which require a new set of tools for testing.

The question for the year 2020 is: “Where do I start with Android testing?”

During this session, I’ll try to go through what we need to do in our apps/libraries to get the tests running, how the most popular Android testing tools work in 2020, which tools and services we can use to automate testing, and finally show you some caveats that come with Kotlin and new architecture approaches I mentioned before.

This can be either a talk or a workshop, both work for me as I have the resources ready.