Does Ktor’s `HttpClient` kick off it’s own corouti...

# ktor

[Ky]

Does Ktor’s HttpClient kick off it’s own coroutine to make requests? And do we have any control over that coroutineContext?

I’m having trouble getting ktors HttpClient to behave nicely in regards to synchronization. Unless I wrap the .get() in withContext(runTest.coroutineContext) my tests do not wait for ktor request to return and the test will complete prematurely

[Aleksei Tirman [JB]]

The HttpClient implements CoroutineScope and has public coroutineContext property.

HttpClient().coroutineContext

[Aleksei Tirman [JB]]

Could you please share the code for your test?

[Ky]

Yes it has coroutine context but it can not be changed.

runTest {
            client.engine.coroutineContext = this.coroutineContext
            viewModel.getMain()
        }

Essentially without wrapping the HttpClient call in withContext(someContext) and setting someContext as TestScope.coroutineContext. The test will complete before HttpClient call returns. I’m having trouble acheiving synchronous mechanism without wrapping in withContext

[Ky]

@Aleksei Tirman [JB]

[Aleksei Tirman [JB]]

Could you please share the definition of the runTest function? In what environment the runTest is executed?

[Piasy]

@Ky If you use MockEngine, you could inject your test dispatcher.

val engine = MockEngine.config {
    dispatcher = StandardTestDispatcher(testScheduler)

    addHandler {
        respondOk(resp)
    }
}

val http = HttpClient(engine)
// inject the http client into your code