aboutsummaryrefslogtreecommitdiffstats
path: root/.coveragerc
diff options
context:
space:
mode:
authorDonald Stufft <donald@stufft.io>2014-11-13 08:17:36 -0500
committerDonald Stufft <donald@stufft.io>2014-11-13 08:17:36 -0500
commit62143e47077b8df78e926da5c8f027d8f01ab281 (patch)
tree374a8d414b7c1fdae7d2ff6b81980e541b59ae12 /.coveragerc
parentc62a78c015cf7aeb0c05bce82ef14cd86fe0b0fc (diff)
downloadcryptography-62143e47077b8df78e926da5c8f027d8f01ab281.tar.gz
cryptography-62143e47077b8df78e926da5c8f027d8f01ab281.tar.bz2
cryptography-62143e47077b8df78e926da5c8f027d8f01ab281.zip
Use coverage parallel mode and coverage combine to fix paths
When using coverage.py with a project installed into site-packages instead of in the current directory you end up with paths like .tox/py34/lib/python3.4/site-packages/cryptography/__init__.py which is less than ideal (and may cause issues when aggregating coverage over multiple versions of Python). Switching coverage.py into parallel-mode will have it write a .coverage.* file instead of a .coverage file, which can then be "combined" into a .coverage file using coverage combine. When coverage.py does the combine step it will collapse the .tox/*/lib/python*/site-packages/cryptography paths into src/cryptography.
Diffstat (limited to '.coveragerc')
-rw-r--r--.coveragerc5
1 files changed, 5 insertions, 0 deletions
diff --git a/.coveragerc b/.coveragerc
index aa69fd4f..a0a57b33 100644
--- a/.coveragerc
+++ b/.coveragerc
@@ -4,6 +4,11 @@ source =
cryptography
tests/
+[paths]
+source =
+ src/cryptography
+ .tox/*/lib/python*/site-packages/cryptography
+
[report]
exclude_lines =
@abc.abstractmethod