Is anyone by chance aware of any threading related changes that were made in

MockEngine

in 1.5.1.....we're updating a client here from a 1.4.x version and have isolated issue we're seeing to update from 1.5.0 to 1.5.1.....we have unit tests that are using

runBlockingTest

and getting

IllegalStateException: This job has not completed yet

after that update....digging deeper to try and narrow in on what's changed but just in case anyone encountered this before....

if you change runBlockingTest to runBlocking, it works?

So, that seems to affect things all right but other part of test fails then.....haven't had chance yet to dig in to that

You can find an explanation here https://youtrack.jetbrains.com/issue/KTOR-2629

so, we can't use

runBlockingTest

for unit tests that use

MockEngine

?

I did encounter the same issue and didn't find a way to solve it. @e5l is there a way to use

runBlockingTest

?

perhaps pattern like following could be used to allow test to inject/replace dispatcher used? https://developer.android.com/kotlin/coroutines/coroutines-best-practices#inject-dispatchers

Hey @John O'Reilly. The problem is caused by context change in MockEngine. Most likely testing library you’re using is not assuming that there are no suspension points in test. It should be some

await

method there. Could you provide the whole code snippet to figure it out?

Hi @e5l, I'm not using any other testing library....just standard unit test with

runBlockingTest

and then testing one of our classes that in turn is using another class that uses

MockEngine

based

HttpClient

. Do you know of any examples/samples etc that are able to use

runBlockingTest

that I can maybe compare to?

Could you check if the code is working with a regular

runBlocking

?

Partly, yes....but running in to other issues then which I'm still trying to get to bottom of

The one problem is that you have to wait for all delays.

fwiw we're injecting

TestCoroutineDispatcher()

when constructing the class under test

Please note:

When switched to lazy execution using pauseDispatcher any coroutines started via launch or async will not execute until a call to DelayController.runCurrent or the virtual clock-time has been advanced via one of the methods on DelayController.

we are using those in some other tests....let me see if/how they can be applied here too