Wrong coverage metrics for FastAPI project

[cashaev]

Hi everyone. I am having an issue with pytest coverage report for my FastAPI project.
Part of the code, which is definitely executed is not market as covered. Namely return statements from routes.

Did anybody here have this issue? I have seen only one mention of it in stackoverflow, but not resolved.
Thank you

[Kludex]

Maybe related to nedbat/coveragepy#1082 ?

[cashaev]

Maybe related to nedbat/coveragepy#1082 ?

@Kludex Yes, looks like it. It was exactly my case: I have a FastAPI together with SQLAlchemy async calls. After reading the thread and other related threads carefully I noticed that coverage report in my project stopped after async calls to SQLAlchemy engine. As I understood the reason for it is that FastAPI uses threads, and SQLAlchemy uses greenlet to provide async behavior and coverage has problems tracking both in the same project.

I tried to play around with the coveragerc settings and came out using "concurrency=greenlet" config. So far, the report looks much better and shows hits on the code lines after SQLAlchemy async calls. I will check it further on.

Thank you for the link. I would definitely not have dug it out by myself!

[dgilmanTORQATA]

I'm also testing against a FastAPI project with a mix of async routes, async SQLAlchemy and synchronous FastAPI dependencies. Instructing coverage to use concurrency = gevent works in async routes that use SQLAlchemy but breaks coverage elsewhere in places like the FastAPI dependencies.

Adding a voodoo await asyncio.sleep(0) right after the last line that coverage picks up on (so right after the line that awaits on a SQLAlchemy coroutine) lets coverage get back up to speed and correctly detect coverage on the following lines.

[stephan-erb-by]

A fix for this has been merged to the coverage repository. Once the new coverage version is out you will be able to specify multiple concurrency options and thus have measurements work out of the box nedbat/coveragepy@c9d821d

[erewok]

After reading the above and making sure I had a recent version of coverage (6.3.1 in my case), I was able to fix this on my project by adding the following to my setup.cfg:

[coverage:run]
concurrency =
  greenlet
  thread

[FilipeMarch]

How do you guys use coverage with FastAPI?
I am executing this on a terminal:

uvicorn app.main:app

And this on another terminal:

pytest -s --cov=. 

I get these results:

But coverage does not show anything about my routes (router.py files):

Some files are showing 0% even though their lines are necessarily being executed (for instance, main.py is where the app starts). I would appreciate some help on how to use coverage correctly with FastAPI.

[Beenhakker]

Any news on this, or what the underlying reason is? We are facing the same issue.