mirror of
https://github.com/tahoe-lafs/tahoe-lafs.git
synced 2024-12-19 04:57:54 +00:00
1593ff5c52
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.
17 lines
299 B
INI
17 lines
299 B
INI
# -*- 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
|