Good asynchronous people. Do we have a way to not ...

# coroutines

[pablisco]

Good asynchronous people. Do we have a way to not use the Android Dispatcher for Dispatchers.Main when running on the test configuration (e.g. Unit tests)

[streetsofboston]

For now, although it is deprecated and will be modified to integrate better in structured concurrency, you could use the TestCoroutineContext.

E.g. instead of SuperviserJob() + Dispatcher.Main you could do SuperviserJob() + testCoroutineContext, where testCoroutineContext is a singleton instance of TestCoroutineContext and you can control it in your unit-test code.

[pablisco]

Yeah, I was hopping to use the default Dispatcher.Main as that one should be ok for the test I'm running instead of the one that is injected by services for android... I'm trying to remove the dependency to coroutines-android for the test configuration 🤔

[Vsevolod Tolstopyatov [JB]]

There will be coroutines-test in 1.1 🙂

[Vsevolod Tolstopyatov [JB]]

https://github.com/Kotlin/kotlinx.coroutines/pull/749/commits/ed0221b634d66c62a5d771eb5c9ee5b84adcfabb

[streetsofboston]

@Vsevolod Tolstopyatov [JB] How will the TestCoroutineContext, or its replacement, fit into this, since it is marked as obsolete/deprecated?

[Vsevolod Tolstopyatov [JB]]

Replacement of TestCoroutineContext will be part of this module, but not in 1.1