Open danielPerez97 opened 1 year ago
This doesn't look like a Turbine issue, no. I have some free advice, though:
shareIn
.runTest
, this
will refer to a TestScope
, which has a backgroundScope
val; inject backgroundScope
as your CoroutineScope
. CoroutineContext
instead of CoroutineDispatcher
; that way, you can inject EmptyCoroutineContext
, which is a no-op under test (it will just use whatever dispatcher is already active). distinctUntilChanged()
before testing your molecule. Happy hunting!
(Apologies if this should be an issue for Turbine) I have the following
BaseViewModel
class which is a lot like the class in the sample-viewmodel folder:Note that
BaseViewModel
does not extend from the AACViewModel
.Here is an implementation of
BaseViewModel
+ composable presenter:This works great inside an actual Android app, but testing it is proving to be a pain with the following failing test:
Which fails with this message:
Here's a test that succeeds, skipping the
PetListViewModel
entirely and using the composable function directly:Am I using a wrong
CoroutineScope
here? I've tried usingTestScope
andCoroutineScope
but no luck. I should note that thePetListViewModel
works great inside an Android app with the following instantiation: