Skip to main content

Using Idling Resources in your Espresso Tests

Using Idling Resources in your Espresso Tests
Testing is wow. And UI testing in Android is awesome. Espresso is a UI testing framework for Android. I can say that it was pretty easy and…

Testing is wow. And UI testing in Android is awesome. Espresso is a UI testing framework for Android. I can say that it was pretty easy and you can get used to it in a couple of hours. It’s just like structured English, but in Java/Kotlin.

A simple example from the documentation when using the Espresso framework is this:

fun greeterSaysHello() {
onView(withText("Hello Steve!")).check(matches(isDisplayed()))
Note: These tests run under the androidtest package.

But sometimes (or mostly) we are not working on the main thread. We have lots of code that blocks our UI and force us to run on another thread. Since Espresso test is quick and straightforward it doesn’t really wait until our background execution has started, is running, is being finished or has already finished. Therefore, we might need a extra hand…

Introducing to the Idling Resources:


From the documentation of the code the Idling Resources are defined like this:

Now Espresso knows how to wait until some heavy work is executing.

Let’s see an example:

First we need a setup for that Idling Resources. Create a class and implement the `IdlingResource` interface:

Basically we are going to tell Espresso to hold when you see an incremented value here, and continue if this value has reached 0

For making things easy create this helper class:

Let’s use it now:

fun onHeavyWorkButtonClicked() {
viewModelScope.launch(Dispatchers.IO) {
//heavy work happens here
withContext(Dispatchers.Main) {

//heavy work has ended

Just another simple step. Now we need to tell the UI test that we are using the IdlingResource on the current view:

And we are good to go. Just test the views as usual! Good luck! 👍👌✔

Note: I’ve also refactored this case in a simple Android package:

Super helpful resource:

Other posts from my blog:

Popular posts from this blog

Modularizing your Android app, breaking the monolith (Part 1)

Inspired by a Martin Fowlers post about Micro Frontends, I decided to break my monolithic app into a modular app. I tried to read a little more about breaking monolithic apps in Android, and as far as I got, I felt confident to share my experience with you. This will be some series of blog posts where we actually try to break a simple app into a modularized Android app.

Note: You should know that I am no expert in this, so if there are false statements or mistakes please feel free to criticize, for the sake of a better development. 

What do you benefit from this approach:
Well, people are moving pretty fast nowadays and delivery is required faster and faster. So, in order to achieve this, modularising Android apps is really necessary.You can share features across different apps. Independent teams and less problems per each.Conditional features update.Quicker debugging and fixing.A feature delay doesn't delay the whole app. As per writing tests, there is not too much difference about…

From Gson to Moshi, what I learned

There is no doubt that people are getting away from GSON and I agree with those reasons too. The only advantage GSON has over other parsing libraries is that it takes a really short amount of time to set up. Furthermore, the most important thing is that Moshi is embracing Kotlin support.

First let's implement the dependency:
implementation("com.squareup.moshi:moshi:1.8.0") It's not a struggle to migrate to Moshi. It's really Gson look-a-like. The only thing to do is annotate the object with @field:Json instead of @SerializedName (which is Gsons way for JS representation):

data class User( //GSON way @SerializedName("name") val name: String, @SerializedName("user_name") val userName: String, @SerializedName("last_name") val lastName: String, @SerializedName("email") val email: String ) data class User( //Moshi way @field:Json(name = "name") val name: String, @field:Json(name = "user_name…

Modularizing your Android app, breaking the monolith (Part 2)

This is part 2 of a series of articles about modularizing Android app. If you haven't yet read the first article, you may find it here.

On our first article we just moved some classes outside the application and applied as an independent module. But what if we have dependencies pulled from the application level? This could be a small challenge. First of all, we want to clarify on how are we going to modularize the app. And depending on the previous article, I chose the by feature version of modularization. First of all, let's show some dependencies that are going to be needed in the whole app.

Note: I'm using Dagger for handling dependencies but manual DI or any dependency tool should be fine to understand this part.

So, this is my dependency schema:

Well, it's not that bad, but this isn't what we want to transform to when trying to modularize the app. If you think about it, modules that don't need a dependency, can get it quite easily. For example: A FeatureXVi…