Test coverage reporting
Use this plugin to activate coverage report.
To use this plugin, you need to install
$ pip install nose2[coverage_plugin]>=0.6.5
Then, you can enable coverage reporting with :
$ nose2 --with-coverage
Or with this lines in
[coverage] always-on = True
You can further specify coverage behaviors with a
.coveragerc file, as
specified by Coverage Config.
However, when doing so you should also be aware of
Differences From coverage.
The default configuration is equivalent to including the following in a
[coverage] always-on = False coverage = coverage-config = coverage-report =
- --coverage PATH
Measure coverage for filesystem path (multi-allowed)
- --coverage-report TYPE
Generate selected reports, available types: term, term-missing, annotate, html, xml (multi-allowed)
- --coverage-config FILE
Config file for coverage, default: .coveragerc
- -C DEFAULT, --with-coverage DEFAULT
Turn on coverage reporting
Plugin class reference: Coverage
- class nose2.plugins.coverage.Coverage(*args, **kwargs)[source]
Reporting data is collected, failure status determined and set. Now print any buffered error output saved from beforeSummaryReport
Start coverage early to catch imported modules.
Only called if active so, safe to just start without checking flags
Differences From coverage
coverage tool is the basis for nose2’s coverage reporting. nose2 will
seek to emulate
coverage behavior whenever possible, but there are known
cases where this is not feasible.
If you need the exact behaviors of
coverage, consider having
Otherwise, please be aware of the following known differences:
fail_underparameter results in an exit status of 2 for
coverage, but an exit status of 1 for
Compatibility with mp plugin
mp plugins may be used in conjunction to enable
multiprocess testing with coverage reporting.
Due to the way the plugin is reloaded in subprocesses, command-line options for the
coverageplugin have no effect. If you need to change any
coverageplugin options, use a configuration file.
Do not use the
concurrencyoption within a
.coveragercfile ; this interferes with the
coverageplugin, which automatically handles multiprocess coverage reporting.