Coverage "No source for code" with pytest

Question

I am trying to measure code coverage by my pytest tests. I tried following the quick start guide of coverage (https://coverage.readthedocs.io/en/6.4.1/)

When I run my test with the following command, everything seems fine

coverage run -m pytest tests/

===================================== test session starts ======================================
platform linux -- Python 3.10.4, pytest-7.1.2, pluggy-1.0.0
rootdir: /home/arnaud/Documents/Github/gotcha
collected 4 items                                                                              

tests/preprocessing/test_preprocessing.py ....                                           [100%]

====================================== 4 passed in 0.30s =======================================

However, when I try to access the report with either of those commands,

coverage report

coverage html

I get the following message:

No source for code: '<project_directory>/config-3.py'.

I did not find an appropriate solution to this problem so far

This might be related to using OpenCV, see the answer below stackoverflow.com/a/77336802/4742780. — Erik
– Erik, Commented Feb 8, 2024 at 15:24

platelminto · Accepted Answer · 2023-01-23 14:55:12Z

4

Another possible solution is to specify the source attribute. In my case, rather than the whole project (source = .), I specified the actual source folder (e.g. src). This can either be done on the commandline:

coverage run --source=src

or include it in your .coveragerc file:

[run]
source = src
...

I was getting this same issue because of a specific library I was importing*, but I never figured out why that library affected coverage, and others didn't.

Though this might just be a workaround, it makes sense to just check your source folder, and ignoring all errors (with -i) isn't much better.

* The library uses opencv-python-headless, which I think has the root cause of this issue.

answered Jan 23, 2023 at 14:55

platelminto

3683 silver badges17 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

arnino · Accepted Answer · 2022-06-17 14:35:20Z

3

It is possible to ignore errors using the command

coverage html -i

which solved my issue

answered Jun 17, 2022 at 14:35

arnino

5607 silver badges22 bronze badges

Comments

omer.hazan · Accepted Answer · 2022-06-17 14:41:56Z

2

This issue is usually caused by older coverage result files, so you can either:

remove the old coverage results files or...
run coverage command with -i flag in order to ignore the errors - you can read more about that in coverage official docs: https://coverage.readthedocs.io/en/6.4.1/cmd.html#reporting

answered Jun 17, 2022 at 14:41

omer.hazan

1492 bronze badges

Comments

browser-bug · Accepted Answer · 2024-02-12 20:32:18Z

2

This is related to https://github.com/nedbat/coveragepy/issues/1653

A temporary solution is to explicitly omit the opencv-python synthetic files that are created at install time.

Add this to your .coveragerc file (or any other configuration file you're using):

omit = 
    config.py
    config-3.py

edited Feb 12, 2024 at 20:32

answered Oct 21, 2023 at 16:06

browser-bug

2,2111 gold badge17 silver badges31 bronze badges

Collectives™ on Stack Overflow

Coverage "No source for code" with pytest

4 Answers 4

Comments

Comments

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

4 Answers 4

Comments

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related