[todo-mvvm-live-kotlin] Espresso idling resource in UITests for livedata?

I was working on a project in which I started using viewmodel and livedata architecture components. I am not using data binding but simply accessing livedata in the activity. While writing the UItest do we need Espresso idling resource for live data so that we can wait for livedata to publish new data?

Review the Android UI testing context around Espresso, LiveData, ViewModel, and the referenced UITests. Determine whether observing LiveData requires an Espresso idling resource, then document the decision and any required testing guidance or example.

Written by the indexing model from the issue text.