Thoughts on using runBlocking in tests instead of ...

# coroutines

[Colton Idle]

Thoughts on using runBlocking in tests instead of runTest? Seems like everything runs fine with runBlocking?

[ross_a]

runTest is more useful when you want to control time, or launch coroutines on a background scope (e.g. stateIn/shareIn) that get cleaned up automatically.

[kevin.cianfarini]

runTest also works on JS and includes built-in timeout functionality.

[Oliver.O]

Or even better – but biased opinion: The test framework should provide you with sensible options and figure it out for you.

[gildor]

runTest also has built it timeout, which is very useful

[Javier]

The default unconfined dispatcher is a bit annoying when you want to test all states without caring about doing some manual delays to avoid conflating, probably the problems you are finding with runTest and are solved with runBlocking can be fixed changing the dispatcher