Configuration for Python test coverage measurement.
--coverage-py-filter="['<str>', '<str>', ...]"
A list of Python modules to use in the coverage report, e.g. `['helloworld_test', 'helloworld.util.dirutil']. The modules are recursive: any submodules will be included. If you leave this off, the coverage report will include every file in the transitive closure of the address/file arguments; for example, `test ::` will include every Python file in your project, whereas `test project/app_test.py` will include `app_test.py` and any of its transitive dependencies.
--coverage-py-report="[<CoverageReportType>, <CoverageReportType>, ...]"
console, xml, html, raw, json
[ "console" ]
Which coverage report type(s) to emit.
Requirement string for the tool.
--coverage-py-extra-requirements="['<str>', '<str>', ...]"
Any additional requirement strings to use with the tool. This is useful if the tool allows you to install plugins or if you need to constrain a dependency to a certain version.
The main module for the tool. If unspecified, the code using this tool must provide it explicitly on invocation, or it can use the tool as a library, invoked by a wrapper script.
--coverage-py-interpreter-constraints="['<str>', '<str>', ...]"
[ "CPython>=3.6" ]
Python interpreter constraints for this tool. An empty list uses the default interpreter constraints for the repo.
Path to write the Pytest Coverage report to. Must be relative to build root.
Path to `.coveragerc` or alternative coverage config file
Updated about a month ago