0

I'm trying to use coverage.py on my unittest-based tests. I see that there are multiple kinds of paths and they're not collated, so the coverage data is wrong.

/home/travis/virtualenv/python3.6.3/lib/python3.6/site-packages/<package>/file.py
/<package>/file.py
something.py

How can I tell coverage.py to treat the paths the same (e.g. to remove the "/home/travis/virtualenv/python3.6.3/lib/python3.6/site-packages" prefix)?

1 Answer 1

0

Create a [paths] section in your configuration file.

Maybe you could help me out: this is easily the most over-looked thing in the coverage.py configuration file. What can I do in the docs to make it more easily found?

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

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.