Did anyone try using `getOrAwayValue()` (the helper function from Google's testing samples) on `Flow...

# flow

[Florian Walther (live streaming)]

Did anyone try using getOrAwayValue() (the helper function from Google's testing samples) on Flow#asLiveData()? I'm not getting a value.

[Florian Walther (live streaming)]

It works if I use UnconfinedTestDispatcher instead of StandardTestDispatcher

[gildor]

Created flow probably asynchronous, so you just get empty live data, this why unconfined dispatcher helps
Why do you convert it to live data?

[Florian Walther (live streaming)]

I use LiveData for the automatic handling of the activity lifecycle

[gildor]

Why you cannot do the same with flow?

[gildor]

I just really think that there is no valid reasons anymore to use livedata if you already has flow in the project

[Florian Walther (live streaming)]

Yea I'm considering switching to Flow but I still didn't just want to ignore the problem. But we found the solution eventually.

[gildor]

I wouldn't call it a problem, rather lack of proper testing facilities for live data.
Testing reactive properties with non reactive tests is always painful and unreliable, because they become testable only when some kind Unconfined dispatchers/schedulers are used for all involved components

[Florian Walther (live streaming)]

Google has a LiveData TestUtil for that which seems to work

[Florian Walther (live streaming)]

The getOrAwaitValue one

[Florian Walther (live streaming)]

But it seems to need UnconfinedTestDispatcher to work

[gildor]

Yes, of course

[gildor]

My point is that getOrAwaitValue is not the best way to test any reactive properties, in any framework

[Florian Walther (live streaming)]

Thank you. I will probably replace LiveData for Flow in the UI layer earlier or later. I just wish I would understand why asLiveData needs UnconfinedTestDispatcher to work.