What is the difference between do ```TestCoroutine...

# coroutines

[Pablo]

What is the difference between do

TestCoroutineScope.runBlockingTest{}

And

TestCoroutineDispatcher.runBlockingTest{}

I see some people use them, and others just put runBlockingText{} without any dispatcher nor coroutineScope, is there any difference?

[gildor]

Scope also includes uncaught exception handler

[gildor]

but it also uses TestCoroutineDispatcher

[gildor]

runBlockingTest is just a top level coroutine which uses TestCoroutineScope, so it convinince method

[Pablo]

Still unclear for me Andrey, you mean that if I use testCoroutineScope.runBlockingTest{..} the exceptions wouldn't be caught? Because I saw other coleagues are using both ways and I'm trying to figure it out what's better or efficient.
Also I'm used to do it without them, like

runBlockingTest {
 my test here
}

[gildor]

just open runBlockingTest implementation, it creates TestCoroutineScope under the hood

[gildor]

also it checks that all jobs started on this scope are finished

[gildor]

the exceptions wouldn’t be caught

no, it’s just records all uncaught exceptions and print stacktrace, just gives a bit more info on crash

[gildor]

actually if you open implementation, all those functions actually do the same, just on different receivers

[gildor]

Top level runBlockingTest is just a good building block, doesn’t require creation of coroutine scope

[Pablo]

That's what I wanted to know 🙂

[Pablo]

runBlockingTest creates everything for you, but I guess they did it like this to ensure, it was running on a TestDispatcher 🤷

[gildor]

but runBlockingTest always run on TestDispatchter until you override it