Testing represents an interesting challenge due to the peculiarities of its technology and the way it eases development for your Android app. LiveData I’ve recently started to build an Android app to keep motivated on my journey to learn . My most recent experience has been with and this brief blog post, in particular, will focus on unit testing your DAO when using . Kotlin Architecture Components [LiveData](https://developer.android.com/jetpack/arch/livedata) What is LiveData? is a lifecycle-aware, observable data holder that will help you react to changes in you data source. In my case, I'm using it in combination with to make sure my app reacts to the new data becoming available in my database. LiveData [Room](https://developer.android.com/jetpack/arch/room) Our simple DAO For this blog post let’s just pretend we have a very simple DAO that looks like the following: This is just a DAO that helps you fetch posts. As you can see, the return type for the function is not just a plain but it wraps it in a instance. This is great because we can get an instance of our list of posts once and then List<Post> [LiveData](https://developer.android.com/reference/android/arch/lifecycle/LiveData) for changes and react to them observe . Let’s test it The Android Developer documentation has a neat example on how to unit test your DAO: This pretty simple test has the aim of testing that the data is being exposed correctly and that, once the post is added to the database, it is reflected by the invocation. getAll() Unfortunately, by the time we are asserting on it, the value of the instance will not be populated and will make our test fail. This is because uses a lifecycle-oriented asynchronous mechanism to populate the underlying data and expects an observer to be registered in order to inform about data changes. LiveData LiveData Observe your data offers a convenient observe method that allows for the data as it changes. We can use it to register an observer that will assert on the expected value. LiveData observing The method has the following signature: observe void observe( owner, <T> observer) LifecycleOwner Observer It expects an observer instance and the owner for its life-cycle. In our case, we’re only interested in keeping the observer around just enough to be able to assert on the changed data. We don’t want the same assertion to be evaluated every time the data changes. Own your lifecycle What we can do, then, is build an observer instance that owns its own life-cycle. After handling the event we will mark the observer life-cycle as destroyed and let the framework do the rest. onChange Let’s see what the observer code looks like: This observer implementation accepts a that will be executed as part of the event. As soon as the handler is complete, its own lifecycle will proceed to mark itself as which will trigger the removal process from the instance. lambda onChange _ON_DESTROY_ LiveData We can then create an extension on LiveData to leverage this kind of observer: fun <T> LiveData<T>.observeOnce(onChangeHandler: (T) -> Unit) {     val observer = OneTimeObserver(handler = onChangeHandler)     observe(observer, observer)} Let’s test it again A couple of things to notice this time. First of all, we’re taking advantage of an . This is a helpful utility rule that takes care of swapping the background asynchronous task executor with a synchronous one. This is vital to be able to deterministically test our code. (Check out if you wanna know more about JUnit rules). [InstantTaskExecutorRule](https://developer.android.com/reference/androidx/arch/core/executor/testing/InstantTaskExecutorRule) this In addition to that, we’re now leveraging the extension that we have written to write our assertions: LiveData postDao.getAll().observeOnce {    assertEquals(0, it.size)} We have just asserted in a much more compact and expressive way by leaving all the details inside our observer implementation. We are now asserting on the instance in a deterministic way making this kind of tests easier to read and write. LiveData Conclusion I hope this post will help you write tests for your DAO more effectively. This is one of my earliest experiences with Kotlin and Android: please, feel free to comment with better approaches to solve this. Cover photo by Irvan Smith on Unsplash

Fetch

Writing a GraphQL DSL in Kotlin

Check out my blog

Nominated for 2022 - HackerNoon Contributor of the Year - Agile

Nominated for 2022 - HackerNoon Contributor of the Year - Agile Software Development

Too Long; Didn't Read

Make resilience your competitive advantage

Testing LiveData on Android

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

Untitled Story

The Best Teams I've Worked With

Java bits: 0xFF and 0xFFL

10 Things You Didn't Know You Could Do With Google Keep

10 Things to check on Android code reviews

10 Mistakes In Mobile App Development That Make You Look Dumb

The Best Teams I've Worked With

Java bits: 0xFF and 0xFFL

10 Things You Didn't Know You Could Do With Google Keep

10 Things to check on Android code reviews

10 Mistakes In Mobile App Development That Make You Look Dumb

Light-Mode

Classic

Newspaper

Dark-Mode

Neon Noir

Minty

HN StartUps