tahoe-lafs/.coveragerc

# -*- mode: conf -*-

[run]
# only record trace data for allmydata.*
source =
       allmydata
# and don't trace the test files themselves, or generated files
omit =
     */allmydata/test/*
     */allmydata/_version.py
parallel = True
branch = True

[report]
show_missing = True
skip_covered = True

[paths]
source =
# It looks like this in the checkout
    src/
# It looks like this in the GitHub Actions Windows build environment
    D:/a/tahoe-lafs/tahoe-lafs/.tox/py*-coverage/Lib/site-packages/
# Although sometimes it looks like this instead.  Also it looks like this on macOS.
    .tox/py*-coverage/lib/python*/site-packages/
# On some Linux CI jobs it looks like this
    /tmp/tahoe-lafs.tox/py*-coverage/lib/python*/site-packages/
tox: add "coverage" environment Run with "tox -e coverage". Uses a new helper module (allmydata.test.run_trial) to let us import+execute trial without knowing exactly where the "trial" binary lives, which helps with using "coverage run" under tox. 2016-05-09 20:59:54 +00:00			`# -- mode: conf --`

			`[run]`
			`# only record trace data for allmydata.*`
			`source =`
			`allmydata`
			`# and don't trace the test files themselves, or generated files`
			`omit =`
			`/allmydata/test/`
			`*/allmydata/_version.py`
add --coverage for integration tests 2019-07-23 16:39:45 +00:00			`parallel = True`
			`branch = True`
test(coverage): Include human-readable coverage report While the XML coverage report is useful for consumption by other tools, such as currently by codecov.io in CI, it's not very useful for humans reviewing the immediate impact of changes on coverage during local development or while monitoring CI output. I don't think running the text report takes much more time so I don't see a downside here. 2020-09-24 18:00:56 +00:00
			`[report]`
			`show_missing = True`
			`skip_covered = True`
Try to convince coverage that all our source files are the same 2020-10-14 16:45:34 +00:00
			`[paths]`
			`source =`
			`# It looks like this in the checkout`
			`src/`
try to match the paths from circleci windows for coverage path rewriting 2023-08-07 21:11:54 +00:00			`# It looks like this in the GitHub Actions Windows build environment`
This is probably a better way to handle multiple Python versions 2020-10-14 17:10:23 +00:00			`D:/a/tahoe-lafs/tahoe-lafs/.tox/py*-coverage/Lib/site-packages/`
Loops like macOS does this too 2020-10-14 17:09:06 +00:00			`# Although sometimes it looks like this instead. Also it looks like this on macOS.`
This is probably a better way to handle multiple Python versions 2020-10-14 17:10:23 +00:00			`.tox/py-coverage/lib/python/site-packages/`
The Linux jobs seem to produce paths like this 2020-10-14 16:58:02 +00:00			`# On some Linux CI jobs it looks like this`
This is probably a better way to handle multiple Python versions 2020-10-14 17:10:23 +00:00			`/tmp/tahoe-lafs.tox/py-coverage/lib/python/site-packages/`