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
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 13:59:54 -07: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 10:39:45 -06: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 11:00:56 -07:00
			`[report]`
			`show_missing = True`
			`skip_covered = True`