TestClient waits for background tasks

Trying to write tests for my app based on Starlette, I noticed that queries I do against my API using TestClient take a long time to complete because the client waits for background tasks spawned on the server.

This behavior slows done my tests unnecessarily, since I don’t care about the completion of those background tasks in most cases. Is there a way to disable it and make the TestClient behave like a normal client of the API?

[scy]

Would there be a relatively easy way to

• still run the background task (i.e. not mock it away)
• make the TestClient request not wait for the background task to finish (i.e. return as soon as the HTTP response is complete) and
• not cancel the background task?

One of my endpoints starts an operation in the background that takes a few seconds to finish. During this time, additional calls to the same endpoint should result in an error. In other words: The endpoint is locked while the operation is running. I want to test that locking behavior by firing a second request while the background task is still running, but I can’t, since the first TestClient request will wait for the task to finish before returning.

I would be fine with TestClient instead waiting for background tasks before the whole test returns (e.g. on TestClient destruction), since my background task doesn’t run that long and it wouldn’t slow my test suite down too much.

[euri10]

Trying to write tests for my app based on Starlette, I noticed that queries I do against my API using TestClient take a long time to complete because the client waits for background tasks spawned on the server.

This behavior slows done my tests unnecessarily, since I don’t care about the completion of those background tasks in most cases. Is there a way to disable it and make the TestClient behave like a normal client of the API?

or you can mock your background tasks @ra-kete and check they’ve been called if hey’re async you can patch using CoroutineMock from asynctest package or wait 3.8