command line usage

When you install, a command-line script simply called coverage is placed in your Python scripts directory. To help with multi-version installs, it will also create either a coverage2 or coverage3 alias, and a coverage-X.Y alias, depending on the version of Python you’re using. For example, when installing on Python 2.7, you will be able to use coverage, coverage2, or coverage-2.7 on the command line. has a number of commands which determine the action performed:

  • run – Run a Python program and collect execution data.
  • report – Report coverage results.
  • html – Produce annotated HTML listings with coverage results.
  • xml – Produce an XML report with coverage results.
  • annotate – Annotate source files with coverage results.
  • erase – Erase previously collected coverage data.
  • combine – Combine together a number of data files.
  • debug – Get diagnostic information.

Help is available with the help command, or with the --help switch on any other command:

$ coverage help
$ coverage help run
$ coverage run --help

Version information for can be displayed with coverage --version.

Any command can use a configuration file by specifying it with the --rcfile=FILE command-line switch. Any option you can set on the command line can also be set in the configuration file. This can be a better way to control since the configuration file can be checked into source control, and can provide options that other invocation techniques (like test runner plugins) may not offer. See Configuration files for more details.


You collect execution data by running your Python program with the run command:

$ coverage run arg1 arg2
blah blah ..your program's output.. blah blah

Your program runs just as if it had been invoked with the Python command line. Arguments after your file name are passed to your program as usual in sys.argv. Rather than providing a file name, you can use the -m switch and specify an importable module name instead, just as you can with the Python -m switch:

$ coverage run -m packagename.modulename arg1 arg2
blah blah ..your program's output.. blah blah

If you want branch coverage measurement, use the --branch flag. Otherwise only statement coverage is measured.

You can specify the code to measure with the --source, --include, and --omit switches. See Specifying source files for details of their interpretation. Remember to put options for run after “run”, but before the program invocation:

$ coverage run --source=dir1,dir2 arg1 arg2
$ coverage run --source=dir1,dir2 -m packagename.modulename arg1 arg2 can measure multi-threaded programs by default. If you are using more exotic concurrency, with the multiprocessing, greenlet, eventlet, or gevent libraries, then will get very confused. Use the --concurrency switch to properly measure programs using these libraries. Give it a value of greenlet, eventlet, or gevent.

By default, does not measure code installed with the Python interpreter, for example, the standard library. If you want to measure that code as well as your own, add the -L flag.

If your coverage results seem to be overlooking code that you know has been executed, try running again with the --timid flag. This uses a simpler but slower trace method. Projects that use DecoratorTools, including TurboGears, will need to use --timid to get correct results.

If you are measuring coverage in a multi-process program, or across a number of machines, you’ll want the --parallel-mode switch to keep the data separate during measurement. See Combining data files below.

During execution, may warn you about conditions it detects that could affect the measurement process. The possible warnings include:

  • “Trace function changed, measurement is likely wrong: XXX”

    Coverage measurement depends on a Python setting called the trace function. Other Python code in your product might change that function, which will disrupt’s measurement. This warning indicate that has happened. The XXX in the message is the new trace function value, which might provide a clue to the cause.

  • “Module XXX has no Python source”

    You asked to measure module XXX, but once it was imported, it turned out not to have a corresponding .py file. Without a .py file, can’t report on missing lines.

  • “Module XXX was never imported”

    You asked to measure module XXX, but it was never imported by your program.

  • “No data was collected” ran your program, but didn’t measure any lines as executed. This could be because you asked to measure only modules that never ran, or for other reasons.

  • “Module XXX was previously imported, but not measured.”

    You asked to measure module XXX, but it had already been imported when coverage started. This meant couldn’t monitor its execution.

Data file collects execution data in a file called ”.coverage”. If need be, you can set a new file name with the COVERAGE_FILE environment variable.

By default,each run of your program starts with an empty data set. If you need to run your program multiple times to get complete data (for example, because you need to supply disjoint options), you can accumulate data across runs with the -a flag on the run command.

To erase the collected data, use the erase command:

$ coverage erase

Combining data files

If you need to collect coverage data from different machines or processes, can combine multiple files into one for reporting.

Once you have created a number of these files, you can copy them all to a single directory, and use the combine command to combine them into one .coverage data file:

$ coverage combine

You can also name directories or files on the command line:

$ combine combine data1.dat windows_data_files/ will collect the data from those places and combine them. The current directory isn’t searched if you use command-line arguments. If you also want data from the current directory, name it explicitly on the command line.

When looks in directories for data files to combine, even the current directory, it only reads files with certain names. It looks for files named the same as the data file (defaulting to ”.coverage”), with a dotted suffix. Here are some examples of data files that can be combined:


The run --parallel-mode switch automatically creates separate data files for each run which can be combined later. The file names include the machine name, the process id, and a random number:


If the different machines run your code from different places in their file systems, won’t know how to combine the data. You can tell how the different locations correlate with a [paths] section in your configuration file. See [paths] for details.

If any data files can’t be read, will print a warning indicating the file and the problem.

Reporting provides a few styles of reporting, with the report, html, annotate, and xml commands. They share a number of common options.

The command-line arguments are module or file names to report on, if you’d like to report on a subset of the data collected.

The --include and --omit flags specify lists of file name patterns. They control which files to report on, and are described in more detail in Specifying source files.

The -i or --ignore-errors switch tells to ignore problems encountered trying to find source files to report on. This can be useful if some files are missing, or if your Python execution is tricky enough that file names are synthesized without real source files.

If you provide a --fail-under value, the total percentage covered will be compared to that value. If it is less, the command will exit with a status code of 2, indicating that the total coverage was less than your target. This can be used as part of a pass/fail condition, for example in a continuous integration server. This option isn’t available for annotate.

Coverage summary

The simplest reporting is a textual summary produced with report:

$ coverage report
Name                      Stmts   Miss  Cover
---------------------------------------------                20      4    80%                 15      2    86%           56      6    89%
TOTAL                        91     12    87%

For each module executed, the report shows the count of executable statements, the number of those statements missed, and the resulting coverage, expressed as a percentage.

The -m flag also shows the line numbers of missing statements:

$ coverage report -m
Name                      Stmts   Miss  Cover   Missing
-------------------------------------------------------                20      4    80%   33-35, 39                 15      2    86%   8, 12           56      6    89%   17-23
TOTAL                        91     12    87%

If you are using branch coverage, then branch statistics will be reported in the Branch and BrPart (for Partial Branch) columns, the Missing column will detail the missed branches:

$ coverage report -m
Name                      Stmts   Miss Branch BrPart  Cover   Missing
---------------------------------------------------------------------                20      4     10      2    80%   33-35, 36->38, 39                 15      2      3      0    86%   8, 12           56      6      5      1    89%   17-23, 40->45
TOTAL                        91     12     18      3    87%

You can restrict the report to only certain files by naming them on the command line:

$ coverage report -m
Name                      Stmts   Miss  Cover   Missing
-------------------------------------------------------                20      4    80%   33-35, 39           56      6    89%   17-23
TOTAL                        76     10    87%

The --skip-covered switch will leave out any file with 100% coverage, letting you focus on the files that still need attention.

Other common reporting options are described above in Reporting.

HTML annotation can annotate your source code for which lines were executed and which were not. The html command creates an HTML report similar to the report summary, but as an HTML file. Each module name links to the source file decorated to show the status of each line.

Here’s a sample report.

Lines are highlighted green for executed, red for missing, and gray for excluded. The counts at the top of the file are buttons to turn on and off the highlighting.

A number of keyboard shortcuts are available for navigating the report. Click the keyboard icon in the upper right to see the complete list.

The title of the report can be set with the title setting in the [html] section of the configuration file, or the --title switch on the command line.

If you prefer a different style for your HTML report, you can provide your own CSS file to apply, by specifying a CSS file in the [html] section of the configuration file. See [html] for details.

The -d argument specifies an output directory, defaulting to “htmlcov”:

$ coverage html -d coverage_html

Other common reporting options are described above in Reporting.

Generating the HTML report can be time-consuming. Stored with the HTML report is a data file that is used to speed up reporting the next time. If you generate a new report into the same directory, will skip generating unchanged pages, making the process faster.

Text annotation

The annotate command produces a text annotation of your source code. With a -d argument specifying an output directory, each Python file becomes a text file in that directory. Without -d, the files are written into the same directories as the original Python files.

Coverage status for each line of source is indicated with a character prefix:

> executed
! missing (not executed)
- excluded

For example:

  # A simple function, never called with x==1

> def h(x):
      """Silly function."""
-     if 0:   #pragma: no cover
-         pass
>     if x == 1:
!         a = 1
>     else:
>         a = 2

Other common reporting options are described above in Reporting.

XML reporting

The xml command writes coverage data to a “coverage.xml” file in a format compatible with Cobertura.

You can specify the name of the output file with the -o switch.

Other common reporting options are described above in Reporting.


The debug command shows internal information to help diagnose problems. If you are reporting a bug about, including the output of this command can often help:

$ coverage debug sys > please_attach_to_bug_report.txt

Two types of information are available: sys to show system configuration, and data to show a summary of the collected coverage data.

The --debug option is available on all commands. It instructs to log internal details of its operation, to help with diagnosing problems. It takes a comma-separated list of options, each indicating a facet of operation to log:

  • callers: annotate each debug message with a stack trace of the callers to that point.
  • config: before starting, dump all the configuration values.
  • dataio: log when reading or writing any data file.
  • dataop: log when data is added to the CoverageData object.
  • pid: annotate all debug output with the process id.
  • plugin: print information about plugin operations.
  • sys: before starting, dump all the system and environment information, as with coverage debug sys.
  • trace: print every decision about whether to trace a file or not. For files not being traced, the reason is also given.

Debug options can also be set with the COVERAGE_DEBUG environment variable, a comma-separated list of these options.

The debug output goes to stderr, unless the COVERAGE_DEBUG_FILE environment variable names a different file, which will be appended to.