@@ -13,6 +13,7 @@ Coverage command line usage
13
13
:history: 20100725T211700, updated for 3.4
14
14
:history: 20110827T212500, updated for 3.5.1, combining aliases
15
15
:history: 20120119T075600, Added some clarification from George Paci
16
+ :history: 20120504T091800, Added info about execution warnings, and 3.5.2 stuff.
16
17
17
18
.. highlight :: console
18
19
@@ -104,14 +105,31 @@ during measurement. See :ref:`cmd_combining` below.
104
105
During execution, coverage.py may warn you about conditions it detects that
105
106
could affect the measurement process. The possible warnings include:
106
107
107
- * "Trace function changed, measurement is likely wrong"
108
+ * "Trace function changed, measurement is likely wrong: XXX "
108
109
109
- * "Module has no Python source"
110
+ Coverage measurement depends on a Python setting called the trace function.
111
+ Other Python code in your product might change that function, which will
112
+ disrupt coverage.py's measurement. This warning indicate that has happened.
113
+ The XXX in the message is the new trace function value, which might provide
114
+ a clue to the cause.
110
115
111
- * "Module was never imported"
116
+ * "Module XXX has no Python source"
117
+
118
+ You asked coverage.py to measure module XXX, but once it was imported, it
119
+ turned out not to have a corresponding .py file. Without a .py file,
120
+ coverage.py can't report on missing lines.
121
+
122
+ * "Module XXX was never imported"
123
+
124
+ You asked coverage.py to measure module XXX, but it was never imported by
125
+ your program.
112
126
113
127
* "No data was collected"
114
128
129
+ Coverage.py ran your program, but didn't measure any lines as executed.
130
+ This could be because you asked to measure only modules that never ran,
131
+ or for other reasons.
132
+
115
133
116
134
117
135
.. _cmd_datafile :
@@ -239,6 +257,10 @@ Lines are highlighted green for executed, red for missing, and gray for
239
257
excluded. The counts at the top of the file are buttons to turn on and off
240
258
the highlighting.
241
259
260
+ If you prefer a different style for your HTML report, you can provide your
261
+ own CSS file to apply, by specifying a CSS file in the [html] section of the
262
+ configuration file. See :ref: `config_html ` for details.
263
+
242
264
A number of keyboard shortcuts are available for navigating the report.
243
265
Click the keyboard icon in the upper right to see the complete list.
244
266
0 commit comments