Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 1 | \section{\module{doctest} --- |
| 2 | Test docstrings represent reality} |
| 3 | |
| 4 | \declaremodule{standard}{doctest} |
| 5 | \moduleauthor{Tim Peters}{tim_one@users.sourceforge.net} |
| 6 | \sectionauthor{Tim Peters}{tim_one@users.sourceforge.net} |
| 7 | \sectionauthor{Moshe Zadka}{moshez@debian.org} |
| 8 | |
| 9 | \modulesynopsis{A framework for verifying examples in docstrings.} |
| 10 | |
| 11 | The \module{doctest} module searches a module's docstrings for text that looks |
| 12 | like an interactive Python session, then executes all such sessions to verify |
| 13 | they still work exactly as shown. Here's a complete but small example: |
| 14 | |
| 15 | \begin{verbatim} |
| 16 | """ |
| 17 | This is module example. |
| 18 | |
| 19 | Example supplies one function, factorial. For example, |
| 20 | |
| 21 | >>> factorial(5) |
| 22 | 120 |
| 23 | """ |
| 24 | |
| 25 | def factorial(n): |
| 26 | """Return the factorial of n, an exact integer >= 0. |
| 27 | |
| 28 | If the result is small enough to fit in an int, return an int. |
| 29 | Else return a long. |
| 30 | |
| 31 | >>> [factorial(n) for n in range(6)] |
| 32 | [1, 1, 2, 6, 24, 120] |
| 33 | >>> [factorial(long(n)) for n in range(6)] |
| 34 | [1, 1, 2, 6, 24, 120] |
| 35 | >>> factorial(30) |
| 36 | 265252859812191058636308480000000L |
| 37 | >>> factorial(30L) |
| 38 | 265252859812191058636308480000000L |
| 39 | >>> factorial(-1) |
| 40 | Traceback (most recent call last): |
| 41 | ... |
| 42 | ValueError: n must be >= 0 |
| 43 | |
| 44 | Factorials of floats are OK, but the float must be an exact integer: |
| 45 | >>> factorial(30.1) |
| 46 | Traceback (most recent call last): |
| 47 | ... |
| 48 | ValueError: n must be exact integer |
| 49 | >>> factorial(30.0) |
| 50 | 265252859812191058636308480000000L |
| 51 | |
| 52 | It must also not be ridiculously large: |
| 53 | >>> factorial(1e100) |
| 54 | Traceback (most recent call last): |
| 55 | ... |
| 56 | OverflowError: n too large |
| 57 | """ |
| 58 | |
| 59 | \end{verbatim} |
| 60 | % allow LaTeX to break here. |
| 61 | \begin{verbatim} |
| 62 | |
| 63 | import math |
| 64 | if not n >= 0: |
| 65 | raise ValueError("n must be >= 0") |
| 66 | if math.floor(n) != n: |
| 67 | raise ValueError("n must be exact integer") |
Raymond Hettinger | 92f21b1 | 2003-07-11 22:32:18 +0000 | [diff] [blame] | 68 | if n+1 == n: # catch a value like 1e300 |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 69 | raise OverflowError("n too large") |
| 70 | result = 1 |
| 71 | factor = 2 |
| 72 | while factor <= n: |
| 73 | try: |
| 74 | result *= factor |
| 75 | except OverflowError: |
| 76 | result *= long(factor) |
| 77 | factor += 1 |
| 78 | return result |
| 79 | |
| 80 | def _test(): |
Tim Peters | c2388a2 | 2004-08-10 01:41:28 +0000 | [diff] [blame] | 81 | import doctest |
| 82 | return doctest.testmod() |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 83 | |
| 84 | if __name__ == "__main__": |
| 85 | _test() |
| 86 | \end{verbatim} |
| 87 | |
Fred Drake | 7a6b4f0 | 2003-07-17 16:00:01 +0000 | [diff] [blame] | 88 | If you run \file{example.py} directly from the command line, |
| 89 | \module{doctest} works its magic: |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 90 | |
| 91 | \begin{verbatim} |
| 92 | $ python example.py |
| 93 | $ |
| 94 | \end{verbatim} |
| 95 | |
Fred Drake | 7a6b4f0 | 2003-07-17 16:00:01 +0000 | [diff] [blame] | 96 | There's no output! That's normal, and it means all the examples |
| 97 | worked. Pass \programopt{-v} to the script, and \module{doctest} |
| 98 | prints a detailed log of what it's trying, and prints a summary at the |
| 99 | end: |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 100 | |
| 101 | \begin{verbatim} |
| 102 | $ python example.py -v |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 103 | Trying: factorial(5) |
| 104 | Expecting: 120 |
| 105 | ok |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 106 | Trying: [factorial(n) for n in range(6)] |
| 107 | Expecting: [1, 1, 2, 6, 24, 120] |
| 108 | ok |
| 109 | Trying: [factorial(long(n)) for n in range(6)] |
| 110 | Expecting: [1, 1, 2, 6, 24, 120] |
Tim Peters | 41a65ea | 2004-08-13 03:55:05 +0000 | [diff] [blame] | 111 | ok |
| 112 | \end{verbatim} |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 113 | |
| 114 | And so on, eventually ending with: |
| 115 | |
| 116 | \begin{verbatim} |
| 117 | Trying: factorial(1e100) |
| 118 | Expecting: |
Tim Peters | c2388a2 | 2004-08-10 01:41:28 +0000 | [diff] [blame] | 119 | Traceback (most recent call last): |
| 120 | ... |
| 121 | OverflowError: n too large |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 122 | ok |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 123 | 2 items passed all tests: |
| 124 | 1 tests in example |
| 125 | 8 tests in example.factorial |
| 126 | 9 tests in 2 items. |
| 127 | 9 passed and 0 failed. |
| 128 | Test passed. |
| 129 | $ |
| 130 | \end{verbatim} |
| 131 | |
Fred Drake | 7a6b4f0 | 2003-07-17 16:00:01 +0000 | [diff] [blame] | 132 | That's all you need to know to start making productive use of |
Tim Peters | 41a65ea | 2004-08-13 03:55:05 +0000 | [diff] [blame] | 133 | \module{doctest}! Jump in. The following sections provide full |
| 134 | details. Note that there are many examples of doctests in |
| 135 | the standard Python test suite and libraries. |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 136 | |
Tim Peters | c2388a2 | 2004-08-10 01:41:28 +0000 | [diff] [blame] | 137 | \subsection{Simple Usage} |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 138 | |
Tim Peters | 41a65ea | 2004-08-13 03:55:05 +0000 | [diff] [blame] | 139 | The simplest way to start using doctest (but not necessarily the way |
| 140 | you'll continue to do it) is to end each module \module{M} with: |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 141 | |
| 142 | \begin{verbatim} |
| 143 | def _test(): |
Tim Peters | c2388a2 | 2004-08-10 01:41:28 +0000 | [diff] [blame] | 144 | import doctest |
| 145 | return doctest.testmod() |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 146 | |
| 147 | if __name__ == "__main__": |
| 148 | _test() |
| 149 | \end{verbatim} |
| 150 | |
Tim Peters | c2388a2 | 2004-08-10 01:41:28 +0000 | [diff] [blame] | 151 | \module{doctest} then examines docstrings in the module calling |
Tim Peters | 41a65ea | 2004-08-13 03:55:05 +0000 | [diff] [blame] | 152 | \function{testmod()}. |
Martin v. Löwis | 4581cfa | 2002-11-22 08:23:09 +0000 | [diff] [blame] | 153 | |
Tim Peters | c2388a2 | 2004-08-10 01:41:28 +0000 | [diff] [blame] | 154 | Running the module as a script causes the examples in the docstrings |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 155 | to get executed and verified: |
| 156 | |
| 157 | \begin{verbatim} |
| 158 | python M.py |
| 159 | \end{verbatim} |
| 160 | |
| 161 | This won't display anything unless an example fails, in which case the |
| 162 | failing example(s) and the cause(s) of the failure(s) are printed to stdout, |
Tim Peters | c2388a2 | 2004-08-10 01:41:28 +0000 | [diff] [blame] | 163 | and the final line of output is |
Tim Peters | 2603960 | 2004-08-13 01:49:12 +0000 | [diff] [blame] | 164 | \samp{'***Test Failed*** \var{N} failures.'}, where \var{N} is the |
Tim Peters | c2388a2 | 2004-08-10 01:41:28 +0000 | [diff] [blame] | 165 | number of examples that failed. |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 166 | |
Fred Drake | 7eb1463 | 2001-02-17 17:32:41 +0000 | [diff] [blame] | 167 | Run it with the \programopt{-v} switch instead: |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 168 | |
| 169 | \begin{verbatim} |
| 170 | python M.py -v |
| 171 | \end{verbatim} |
| 172 | |
Fred Drake | 8836e56 | 2003-07-17 15:22:47 +0000 | [diff] [blame] | 173 | and a detailed report of all examples tried is printed to standard |
| 174 | output, along with assorted summaries at the end. |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 175 | |
Tim Peters | c2388a2 | 2004-08-10 01:41:28 +0000 | [diff] [blame] | 176 | You can force verbose mode by passing \code{verbose=True} to |
Fred Drake | 5d2f515 | 2003-06-28 03:09:06 +0000 | [diff] [blame] | 177 | \function{testmod()}, or |
Tim Peters | c2388a2 | 2004-08-10 01:41:28 +0000 | [diff] [blame] | 178 | prohibit it by passing \code{verbose=False}. In either of those cases, |
Fred Drake | 5d2f515 | 2003-06-28 03:09:06 +0000 | [diff] [blame] | 179 | \code{sys.argv} is not examined by \function{testmod()}. |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 180 | |
Fred Drake | 5d2f515 | 2003-06-28 03:09:06 +0000 | [diff] [blame] | 181 | In any case, \function{testmod()} returns a 2-tuple of ints \code{(\var{f}, |
Fred Drake | 7eb1463 | 2001-02-17 17:32:41 +0000 | [diff] [blame] | 182 | \var{t})}, where \var{f} is the number of docstring examples that |
| 183 | failed and \var{t} is the total number of docstring examples |
| 184 | attempted. |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 185 | |
| 186 | \subsection{Which Docstrings Are Examined?} |
| 187 | |
Tim Peters | 8a3b69c | 2004-08-12 22:31:25 +0000 | [diff] [blame] | 188 | The module docstring, and all function, class and method docstrings are |
| 189 | searched. Objects imported into the module are not searched. |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 190 | |
Fred Drake | 7eb1463 | 2001-02-17 17:32:41 +0000 | [diff] [blame] | 191 | In addition, if \code{M.__test__} exists and "is true", it must be a |
| 192 | dict, and each entry maps a (string) name to a function object, class |
| 193 | object, or string. Function and class object docstrings found from |
Tim Peters | 8a3b69c | 2004-08-12 22:31:25 +0000 | [diff] [blame] | 194 | \code{M.__test__} are searched, and strings are treated as if they |
| 195 | were docstrings. In output, a key \code{K} in \code{M.__test__} appears |
| 196 | with name |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 197 | |
| 198 | \begin{verbatim} |
Fred Drake | 8836e56 | 2003-07-17 15:22:47 +0000 | [diff] [blame] | 199 | <name of M>.__test__.K |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 200 | \end{verbatim} |
| 201 | |
| 202 | Any classes found are recursively searched similarly, to test docstrings in |
Tim Peters | 8a3b69c | 2004-08-12 22:31:25 +0000 | [diff] [blame] | 203 | their contained methods and nested classes. |
| 204 | |
| 205 | \versionchanged[A "private name" concept is deprecated and no longer |
Tim Peters | 2603960 | 2004-08-13 01:49:12 +0000 | [diff] [blame] | 206 | documented]{2.4} |
Tim Peters | 8a3b69c | 2004-08-12 22:31:25 +0000 | [diff] [blame] | 207 | |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 208 | |
| 209 | \subsection{What's the Execution Context?} |
| 210 | |
Tim Peters | 41a65ea | 2004-08-13 03:55:05 +0000 | [diff] [blame] | 211 | By default, each time \function{testmod()} finds a docstring to test, it |
| 212 | uses a \emph{shallow copy} of \module{M}'s globals, so that running tests |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 213 | doesn't change the module's real globals, and so that one test in |
| 214 | \module{M} can't leave behind crumbs that accidentally allow another test |
| 215 | to work. This means examples can freely use any names defined at top-level |
Tim Peters | 0481d24 | 2001-10-02 21:01:22 +0000 | [diff] [blame] | 216 | in \module{M}, and names defined earlier in the docstring being run. |
Tim Peters | 41a65ea | 2004-08-13 03:55:05 +0000 | [diff] [blame] | 217 | Examples cannot see names defined in other docstrings. |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 218 | |
| 219 | You can force use of your own dict as the execution context by passing |
Tim Peters | 41a65ea | 2004-08-13 03:55:05 +0000 | [diff] [blame] | 220 | \code{globs=your_dict} to \function{testmod()} instead. |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 221 | |
| 222 | \subsection{What About Exceptions?} |
| 223 | |
Tim Peters | 41a65ea | 2004-08-13 03:55:05 +0000 | [diff] [blame] | 224 | No problem: just paste in the expected traceback. Since |
| 225 | tracebacks contain details that are likely to change |
| 226 | rapidly (for example, exact file paths and line numbers), this is one |
| 227 | case where doctest works hard to be flexible in what it accepts. |
| 228 | This makes the full story involved, but you really don't have |
| 229 | to remember much. Simple example: |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 230 | |
| 231 | \begin{verbatim} |
Fred Drake | 19f3c52 | 2001-02-22 23:15:05 +0000 | [diff] [blame] | 232 | >>> [1, 2, 3].remove(42) |
| 233 | Traceback (most recent call last): |
| 234 | File "<stdin>", line 1, in ? |
| 235 | ValueError: list.remove(x): x not in list |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 236 | \end{verbatim} |
| 237 | |
Tim Peters | 41a65ea | 2004-08-13 03:55:05 +0000 | [diff] [blame] | 238 | That doctest succeeds if, and only if, \exception{ValueError} is raised, |
| 239 | with the \samp{list.remove(x): x not in list} detail as shown. |
| 240 | |
| 241 | The expected output for an exception is divided into four parts. |
| 242 | First, an example may produce some normal output before an exception |
| 243 | is raised, although that's unusual. The "normal output" is taken to |
| 244 | be everything until the first "Traceback" line, and is usually an |
| 245 | empty string. Next, the traceback line must be one of these two, and |
| 246 | indented the same as the first line in the example: |
| 247 | |
| 248 | \begin{verbatim} |
| 249 | Traceback (most recent call last): |
| 250 | Traceback (innermost last): |
| 251 | \end{verbatim} |
| 252 | |
| 253 | The most interesting part is the last part: the line(s) starting with the |
| 254 | exception type and detail. This is usually the last line of a traceback, |
| 255 | but can extend across any number of lines. After the "Traceback" line, |
| 256 | doctest simply ignores everything until the first line indented the same as |
| 257 | the first line of the example, \emph{and} starting with an alphanumeric |
| 258 | character. This example illustrates the complexities that are possible: |
| 259 | |
| 260 | \begin{verbatim} |
| 261 | >>> print 1, 2; raise ValueError('printed 1\nand 2\n but not 3') |
| 262 | 1 2 |
| 263 | Traceback (most recent call last): |
| 264 | ... indented the same, but doesn't start with an alphanumeric |
| 265 | not indented the same, so ignored too |
| 266 | File "/Python23/lib/doctest.py", line 442, in _run_examples_inner |
| 267 | compileflags, 1) in globs |
| 268 | File "<string>", line 1, in ? # and all these are ignored |
| 269 | ValueError: printed 1 |
| 270 | and 2 |
| 271 | but not 3 |
| 272 | \end{verbatim} |
| 273 | |
| 274 | The first (\samp{1 2}) and last three (starting with |
| 275 | \exception{ValueError}) lines are compared, and the rest are ignored. |
| 276 | |
| 277 | Best practice is to omit the ``File'' lines, unless they add |
| 278 | significant documentation value to the example. So the example above |
| 279 | is probably better as: |
| 280 | |
| 281 | \begin{verbatim} |
| 282 | >>> print 1, 2; raise ValueError('printed 1\nand 2\n but not 3') |
| 283 | 1 2 |
| 284 | Traceback (most recent call last): |
| 285 | ... |
| 286 | ValueError: printed 1 |
| 287 | and 2 |
| 288 | but not 3 |
| 289 | \end{verbatim} |
| 290 | |
| 291 | Note the tracebacks are treated very specially. In particular, in the |
| 292 | rewritten example, the use of \samp{...} is independent of doctest's |
| 293 | \constant{ELLIPSIS} option. The ellipsis in that example could |
| 294 | be left out, or could just as well be three (or three hundred) commas. |
| 295 | |
| 296 | \versionchanged[The abilities to check both normal output and an |
| 297 | exception in a single example, and to have a multi-line |
| 298 | exception detail, were added]{2.4} |
| 299 | |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 300 | |
Tim Peters | 026f8dc | 2004-08-19 16:38:58 +0000 | [diff] [blame] | 301 | \subsection{Option Flags and Directives\label{doctest-options}} |
Tim Peters | 8a3b69c | 2004-08-12 22:31:25 +0000 | [diff] [blame] | 302 | |
Tim Peters | 83e259a | 2004-08-13 21:55:21 +0000 | [diff] [blame] | 303 | A number of option flags control various aspects of doctest's comparison |
Tim Peters | 026f8dc | 2004-08-19 16:38:58 +0000 | [diff] [blame] | 304 | behavior. Symbolic names for the flags are supplied as module constants, |
Tim Peters | 83e259a | 2004-08-13 21:55:21 +0000 | [diff] [blame] | 305 | which can be or'ed together and passed to various functions. The names |
Tim Peters | 026f8dc | 2004-08-19 16:38:58 +0000 | [diff] [blame] | 306 | can also be used in doctest directives (see below). |
Tim Peters | 8a3b69c | 2004-08-12 22:31:25 +0000 | [diff] [blame] | 307 | |
| 308 | \begin{datadesc}{DONT_ACCEPT_TRUE_FOR_1} |
| 309 | By default, if an expected output block contains just \code{1}, |
| 310 | an actual output block containing just \code{1} or just |
| 311 | \code{True} is considered to be a match, and similarly for \code{0} |
| 312 | versus \code{False}. When \constant{DONT_ACCEPT_TRUE_FOR_1} is |
| 313 | specified, neither substitution is allowed. The default behavior |
| 314 | caters to that Python changed the return type of many functions |
| 315 | from integer to boolean; doctests expecting "little integer" |
| 316 | output still work in these cases. This option will probably go |
| 317 | away, but not for several years. |
| 318 | \end{datadesc} |
| 319 | |
| 320 | \begin{datadesc}{DONT_ACCEPT_BLANKLINE} |
| 321 | By default, if an expected output block contains a line |
| 322 | containing only the string \code{<BLANKLINE>}, then that line |
| 323 | will match a blank line in the actual output. Because a |
| 324 | genuinely blank line delimits the expected output, this is |
| 325 | the only way to communicate that a blank line is expected. When |
| 326 | \constant{DONT_ACCEPT_BLANKLINE} is specified, this substitution |
| 327 | is not allowed. |
| 328 | \end{datadesc} |
| 329 | |
| 330 | \begin{datadesc}{NORMALIZE_WHITESPACE} |
| 331 | When specified, all sequences of whitespace (blanks and newlines) are |
| 332 | treated as equal. Any sequence of whitespace within the expected |
| 333 | output will match any sequence of whitespace within the actual output. |
| 334 | By default, whitespace must match exactly. |
| 335 | \constant{NORMALIZE_WHITESPACE} is especially useful when a line |
| 336 | of expected output is very long, and you want to wrap it across |
| 337 | multiple lines in your source. |
| 338 | \end{datadesc} |
| 339 | |
| 340 | \begin{datadesc}{ELLIPSIS} |
| 341 | When specified, an ellipsis marker (\code{...}) in the expected output |
| 342 | can match any substring in the actual output. This includes |
Tim Peters | 026f8dc | 2004-08-19 16:38:58 +0000 | [diff] [blame] | 343 | substrings that span line boundaries, and empty substrings, so it's |
| 344 | best to keep usage of this simple. Complicated uses can lead to the |
| 345 | same kinds of "oops, it matched too much!" surprises that \regexp{.*} |
| 346 | is prone to in regular expressions. |
Tim Peters | 8a3b69c | 2004-08-12 22:31:25 +0000 | [diff] [blame] | 347 | \end{datadesc} |
| 348 | |
| 349 | \begin{datadesc}{UNIFIED_DIFF} |
| 350 | When specified, failures that involve multi-line expected and |
| 351 | actual outputs are displayed using a unified diff. |
| 352 | \end{datadesc} |
| 353 | |
| 354 | \begin{datadesc}{CONTEXT_DIFF} |
| 355 | When specified, failures that involve multi-line expected and |
| 356 | actual outputs will be displayed using a context diff. |
| 357 | \end{datadesc} |
| 358 | |
| 359 | |
Tim Peters | 026f8dc | 2004-08-19 16:38:58 +0000 | [diff] [blame] | 360 | A "doctest directive" is a trailing Python comment on a line of a doctest |
| 361 | example: |
| 362 | |
| 363 | \begin{productionlist}[doctest] |
| 364 | \production{directive} |
Johannes Gijsbers | c890618 | 2004-08-20 14:37:05 +0000 | [diff] [blame] | 365 | {"\#" "doctest:" \token{on_or_off} \token{directive_name}} |
Tim Peters | 026f8dc | 2004-08-19 16:38:58 +0000 | [diff] [blame] | 366 | \production{on_or_off} |
| 367 | {"+" | "-"} |
| 368 | \production{directive_name} |
| 369 | {"DONT_ACCEPT_BLANKLINE" | "NORMALIZE_WHITESPACE" | ...} |
| 370 | \end{productionlist} |
| 371 | |
| 372 | Whitespace is not allowed between the \code{+} or \code{-} and the |
| 373 | directive name. The directive name can be any of the option names |
| 374 | explained above. |
| 375 | |
| 376 | The doctest directives appearing in a single example modify doctest's |
| 377 | behavior for that single example. Use \code{+} to enable the named |
| 378 | behavior, or \code{-} to disable it. |
| 379 | |
| 380 | For example, this test passes: |
| 381 | |
| 382 | \begin{verbatim} |
| 383 | >>> print range(20) #doctest: +NORMALIZE_WHITESPACE |
| 384 | [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, |
| 385 | 10, 11, 12, 13, 14, 15, 16, 17, 18, 19] |
| 386 | \end{verbatim} |
| 387 | |
| 388 | Without the directive it would fail, both because the actual output |
| 389 | doesn't have two blanks before the single-digit list elements, and |
| 390 | because the actual output is on a single line. This test also passes, |
| 391 | and requires a directive to do so: |
| 392 | |
| 393 | \begin{verbatim} |
| 394 | >>> print range(20) # doctest:+ELLIPSIS |
| 395 | [0, 1, ..., 18, 19] |
| 396 | \end{verbatim} |
| 397 | |
| 398 | Only one directive per physical line is accepted. If you want to |
| 399 | use multiple directives for a single example, you can add |
| 400 | \samp{...} lines to your example containing only directives: |
| 401 | |
| 402 | \begin{verbatim} |
| 403 | >>> print range(20) #doctest: +ELLIPSIS |
| 404 | ... #doctest: +NORMALIZE_WHITESPACE |
| 405 | [0, 1, ..., 18, 19] |
| 406 | \end{verbatim} |
| 407 | |
| 408 | Note that since all options are disabled by default, and directives apply |
| 409 | only to the example they appear in, enabling options (via \code{+} in a |
| 410 | directive) is usually the only meaningful choice. However, option flags |
| 411 | can also be passed to functions that run doctests, establishing different |
| 412 | defaults. In such cases, disabling an option via \code{-} in a directive |
| 413 | can be useful. |
| 414 | |
Tim Peters | 8a3b69c | 2004-08-12 22:31:25 +0000 | [diff] [blame] | 415 | \versionchanged[Constants \constant{DONT_ACCEPT_BLANKLINE}, |
| 416 | \constant{NORMALIZE_WHITESPACE}, \constant{ELLIPSIS}, |
| 417 | \constant{UNIFIED_DIFF}, and \constant{CONTEXT_DIFF} |
Tim Peters | 026f8dc | 2004-08-19 16:38:58 +0000 | [diff] [blame] | 418 | were added; by default \code{<BLANKLINE>} in expected output |
| 419 | matches an empty line in actual output; and doctest directives |
| 420 | were added]{2.4} |
| 421 | |
Tim Peters | 8a3b69c | 2004-08-12 22:31:25 +0000 | [diff] [blame] | 422 | |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 423 | \subsection{Advanced Usage} |
| 424 | |
Raymond Hettinger | 92f21b1 | 2003-07-11 22:32:18 +0000 | [diff] [blame] | 425 | Several module level functions are available for controlling how doctests |
| 426 | are run. |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 427 | |
Raymond Hettinger | 92f21b1 | 2003-07-11 22:32:18 +0000 | [diff] [blame] | 428 | \begin{funcdesc}{debug}{module, name} |
| 429 | Debug a single docstring containing doctests. |
| 430 | |
| 431 | Provide the \var{module} (or dotted name of the module) containing the |
| 432 | docstring to be debugged and the \var{name} (within the module) of the |
| 433 | object with the docstring to be debugged. |
| 434 | |
| 435 | The doctest examples are extracted (see function \function{testsource()}), |
| 436 | and written to a temporary file. The Python debugger, \refmodule{pdb}, |
Fred Drake | 8836e56 | 2003-07-17 15:22:47 +0000 | [diff] [blame] | 437 | is then invoked on that file. |
Raymond Hettinger | 92f21b1 | 2003-07-11 22:32:18 +0000 | [diff] [blame] | 438 | \versionadded{2.3} |
| 439 | \end{funcdesc} |
| 440 | |
Tim Peters | 83e259a | 2004-08-13 21:55:21 +0000 | [diff] [blame] | 441 | \begin{funcdesc}{testmod}{\optional{m}\optional{, name}\optional{, |
| 442 | globs}\optional{, verbose}\optional{, |
| 443 | isprivate}\optional{, report}\optional{, |
| 444 | optionflags}\optional{, extraglobs}\optional{, |
| 445 | raise_on_error}} |
Raymond Hettinger | 92f21b1 | 2003-07-11 22:32:18 +0000 | [diff] [blame] | 446 | |
Tim Peters | 83e259a | 2004-08-13 21:55:21 +0000 | [diff] [blame] | 447 | All arguments are optional, and all except for \var{m} should be |
| 448 | specified in keyword form. |
| 449 | |
| 450 | Test examples in docstrings in functions and classes reachable |
| 451 | from module \var{m} (or the current module if \var{m} is not supplied |
| 452 | or is \code{None}), starting with \code{\var{m}.__doc__}. |
| 453 | |
| 454 | Also test examples reachable from dict \code{\var{m}.__test__}, if it |
| 455 | exists and is not \code{None}. \code{\var{m}.__test__} maps |
| 456 | names (strings) to functions, classes and strings; function and class |
| 457 | docstrings are searched for examples; strings are searched directly, |
| 458 | as if they were docstrings. |
| 459 | |
| 460 | Only docstrings attached to objects belonging to module \var{m} are |
| 461 | searched. |
| 462 | |
| 463 | Return \samp{(\var{failure_count}, \var{test_count})}. |
| 464 | |
| 465 | Optional argument \var{name} gives the name of the module; by default, |
| 466 | or if \code{None}, \code{\var{m}.__name__} is used. |
| 467 | |
| 468 | Optional argument \var{globs} gives a dict to be used as the globals |
| 469 | when executing examples; by default, or if \code{None}, |
| 470 | \code{\var{m}.__dict__} is used. A new shallow copy of this dict is |
| 471 | created for each docstring with examples, so that each docstring's |
| 472 | examples start with a clean slate. |
| 473 | |
| 474 | Optional argument \var{extraglobs} gives a dict merged into the |
| 475 | globals used to execute examples. This works like |
| 476 | \method{dict.update()}: if \var{globs} and \var{extraglobs} have a |
| 477 | common key, the associated value in \var{extraglobs} appears in the |
| 478 | combined dict. By default, or if \code{None}, no extra globals are |
| 479 | used. This is an advanced feature that allows parameterization of |
| 480 | doctests. For example, a doctest can be written for a base class, using |
| 481 | a generic name for the class, then reused to test any number of |
| 482 | subclasses by passing an \var{extraglobs} dict mapping the generic |
| 483 | name to the subclass to be tested. |
| 484 | |
| 485 | Optional argument \var{verbose} prints lots of stuff if true, and prints |
| 486 | only failures if false; by default, or if \code{None}, it's true |
| 487 | if and only if \code{'-v'} is in \code{sys.argv}. |
| 488 | |
| 489 | Optional argument \var{report} prints a summary at the end when true, |
| 490 | else prints nothing at the end. In verbose mode, the summary is |
| 491 | detailed, else the summary is very brief (in fact, empty if all tests |
| 492 | passed). |
| 493 | |
| 494 | Optional argument \var{optionflags} or's together option flags. See |
| 495 | see section \ref{doctest-options}. |
| 496 | |
| 497 | Optional argument \var{raise_on_error} defaults to false. If true, |
| 498 | an exception is raised upon the first failure or unexpected exception |
| 499 | in an example. This allows failures to be post-mortem debugged. |
| 500 | Default behavior is to continue running examples. |
| 501 | |
| 502 | Optional argument \var{isprivate} specifies a function used to |
| 503 | determine whether a name is private. The default function treats |
| 504 | all names as public. \var{isprivate} can be set to |
| 505 | \code{doctest.is_private} to skip over names that are |
| 506 | private according to Python's underscore naming convention. |
| 507 | \deprecated{2.4}{\var{isprivate} was a stupid idea -- don't use it. |
| 508 | If you need to skip tests based on name, filter the list returned by |
| 509 | \code{DocTestFinder.find()} instead.} |
| 510 | |
| 511 | \versionchanged[The parameter \var{optionflags} was added]{2.3} |
| 512 | |
| 513 | \versionchanged[The parameters \var{extraglobs} and \var{raise_on_error} |
| 514 | were added]{2.4} |
Raymond Hettinger | 92f21b1 | 2003-07-11 22:32:18 +0000 | [diff] [blame] | 515 | \end{funcdesc} |
| 516 | |
| 517 | \begin{funcdesc}{testsource}{module, name} |
| 518 | Extract the doctest examples from a docstring. |
| 519 | |
| 520 | Provide the \var{module} (or dotted name of the module) containing the |
| 521 | tests to be extracted and the \var{name} (within the module) of the object |
| 522 | with the docstring containing the tests to be extracted. |
| 523 | |
| 524 | The doctest examples are returned as a string containing Python |
| 525 | code. The expected output blocks in the examples are converted |
| 526 | to Python comments. |
| 527 | \versionadded{2.3} |
| 528 | \end{funcdesc} |
| 529 | |
| 530 | \begin{funcdesc}{DocTestSuite}{\optional{module}} |
Fred Drake | 7a6b4f0 | 2003-07-17 16:00:01 +0000 | [diff] [blame] | 531 | Convert doctest tests for a module to a |
| 532 | \class{\refmodule{unittest}.TestSuite}. |
Raymond Hettinger | 92f21b1 | 2003-07-11 22:32:18 +0000 | [diff] [blame] | 533 | |
| 534 | The returned \class{TestSuite} is to be run by the unittest framework |
| 535 | and runs each doctest in the module. If any of the doctests fail, |
| 536 | then the synthesized unit test fails, and a \exception{DocTestTestFailure} |
| 537 | exception is raised showing the name of the file containing the test and a |
| 538 | (sometimes approximate) line number. |
| 539 | |
| 540 | The optional \var{module} argument provides the module to be tested. It |
| 541 | can be a module object or a (possibly dotted) module name. If not |
Fred Drake | 8836e56 | 2003-07-17 15:22:47 +0000 | [diff] [blame] | 542 | specified, the module calling this function is used. |
Raymond Hettinger | 92f21b1 | 2003-07-11 22:32:18 +0000 | [diff] [blame] | 543 | |
| 544 | Example using one of the many ways that the \refmodule{unittest} module |
| 545 | can use a \class{TestSuite}: |
| 546 | |
| 547 | \begin{verbatim} |
| 548 | import unittest |
| 549 | import doctest |
| 550 | import my_module_with_doctests |
| 551 | |
| 552 | suite = doctest.DocTestSuite(my_module_with_doctests) |
| 553 | runner = unittest.TextTestRunner() |
| 554 | runner.run(suite) |
| 555 | \end{verbatim} |
| 556 | |
| 557 | \versionadded{2.3} |
Fred Drake | 8836e56 | 2003-07-17 15:22:47 +0000 | [diff] [blame] | 558 | \warning{This function does not currently search \code{M.__test__} |
Raymond Hettinger | 943277e | 2003-07-17 14:47:12 +0000 | [diff] [blame] | 559 | and its search technique does not exactly match \function{testmod()} in |
| 560 | every detail. Future versions will bring the two into convergence.} |
Raymond Hettinger | 92f21b1 | 2003-07-11 22:32:18 +0000 | [diff] [blame] | 561 | \end{funcdesc} |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 562 | |
| 563 | |
| 564 | \subsection{How are Docstring Examples Recognized?} |
| 565 | |
Fred Drake | 7a6b4f0 | 2003-07-17 16:00:01 +0000 | [diff] [blame] | 566 | In most cases a copy-and-paste of an interactive console session works |
Tim Peters | 83e259a | 2004-08-13 21:55:21 +0000 | [diff] [blame] | 567 | fine, but doctest isn't trying to do an exact emulation of any specific |
| 568 | Python shell. All hard tab characters are expanded to spaces, using |
| 569 | 8-column tab stops. If you don't believe tabs should mean that, too |
| 570 | bad: don't use hard tabs, or write your own \class{DocTestParser} |
| 571 | class. |
| 572 | |
| 573 | \versionchanged[Expanding tabs to spaces is new; previous versions |
| 574 | tried to preserve hard tabs, with confusing results]{2.4} |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 575 | |
| 576 | \begin{verbatim} |
Fred Drake | 19f3c52 | 2001-02-22 23:15:05 +0000 | [diff] [blame] | 577 | >>> # comments are ignored |
| 578 | >>> x = 12 |
| 579 | >>> x |
| 580 | 12 |
| 581 | >>> if x == 13: |
| 582 | ... print "yes" |
| 583 | ... else: |
| 584 | ... print "no" |
| 585 | ... print "NO" |
| 586 | ... print "NO!!!" |
| 587 | ... |
| 588 | no |
| 589 | NO |
| 590 | NO!!! |
| 591 | >>> |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 592 | \end{verbatim} |
| 593 | |
Fred Drake | 19f3c52 | 2001-02-22 23:15:05 +0000 | [diff] [blame] | 594 | Any expected output must immediately follow the final |
| 595 | \code{'>\code{>}>~'} or \code{'...~'} line containing the code, and |
| 596 | the expected output (if any) extends to the next \code{'>\code{>}>~'} |
| 597 | or all-whitespace line. |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 598 | |
| 599 | The fine print: |
| 600 | |
| 601 | \begin{itemize} |
| 602 | |
| 603 | \item Expected output cannot contain an all-whitespace line, since such a |
Tim Peters | 83e259a | 2004-08-13 21:55:21 +0000 | [diff] [blame] | 604 | line is taken to signal the end of expected output. If expected |
| 605 | output does contain a blank line, put \code{<BLANKLINE>} in your |
| 606 | doctest example each place a blank line is expected. |
| 607 | \versionchanged[\code{<BLANKLINE>} was added; there was no way to |
| 608 | use expected output containing empty lines in |
| 609 | previous versions]{2.4} |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 610 | |
| 611 | \item Output to stdout is captured, but not output to stderr (exception |
| 612 | tracebacks are captured via a different means). |
| 613 | |
Martin v. Löwis | 92816de | 2004-05-31 19:01:00 +0000 | [diff] [blame] | 614 | \item If you continue a line via backslashing in an interactive session, |
| 615 | or for any other reason use a backslash, you should use a raw |
| 616 | docstring, which will preserve your backslahses exactly as you type |
| 617 | them: |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 618 | |
| 619 | \begin{verbatim} |
Tim Peters | 336689b | 2004-07-23 02:48:24 +0000 | [diff] [blame] | 620 | >>> def f(x): |
Martin v. Löwis | 92816de | 2004-05-31 19:01:00 +0000 | [diff] [blame] | 621 | ... r'''Backslashes in a raw docstring: m\n''' |
| 622 | >>> print f.__doc__ |
| 623 | Backslashes in a raw docstring: m\n |
| 624 | \end{verbatim} |
Tim Peters | 336689b | 2004-07-23 02:48:24 +0000 | [diff] [blame] | 625 | |
Martin v. Löwis | 92816de | 2004-05-31 19:01:00 +0000 | [diff] [blame] | 626 | Otherwise, the backslash will be interpreted as part of the string. |
| 627 | E.g., the "\textbackslash" above would be interpreted as a newline |
| 628 | character. Alternatively, you can double each backslash in the |
| 629 | doctest version (and not use a raw string): |
| 630 | |
| 631 | \begin{verbatim} |
Tim Peters | 336689b | 2004-07-23 02:48:24 +0000 | [diff] [blame] | 632 | >>> def f(x): |
Martin v. Löwis | 92816de | 2004-05-31 19:01:00 +0000 | [diff] [blame] | 633 | ... '''Backslashes in a raw docstring: m\\n''' |
| 634 | >>> print f.__doc__ |
| 635 | Backslashes in a raw docstring: m\n |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 636 | \end{verbatim} |
| 637 | |
Tim Peters | f0768c8 | 2001-02-20 10:57:30 +0000 | [diff] [blame] | 638 | \item The starting column doesn't matter: |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 639 | |
| 640 | \begin{verbatim} |
Tim Peters | c4089d8 | 2001-02-17 18:03:25 +0000 | [diff] [blame] | 641 | >>> assert "Easy!" |
| 642 | >>> import math |
| 643 | >>> math.floor(1.9) |
| 644 | 1.0 |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 645 | \end{verbatim} |
| 646 | |
Fred Drake | 19f3c52 | 2001-02-22 23:15:05 +0000 | [diff] [blame] | 647 | and as many leading whitespace characters are stripped from the |
| 648 | expected output as appeared in the initial \code{'>\code{>}>~'} line |
Tim Peters | 83e259a | 2004-08-13 21:55:21 +0000 | [diff] [blame] | 649 | that started the example. |
Fred Drake | 7eb1463 | 2001-02-17 17:32:41 +0000 | [diff] [blame] | 650 | \end{itemize} |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 651 | |
| 652 | \subsection{Warnings} |
| 653 | |
| 654 | \begin{enumerate} |
| 655 | |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 656 | \item \module{doctest} is serious about requiring exact matches in expected |
| 657 | output. If even a single character doesn't match, the test fails. This |
| 658 | will probably surprise you a few times, as you learn exactly what Python |
| 659 | does and doesn't guarantee about output. For example, when printing a |
| 660 | dict, Python doesn't guarantee that the key-value pairs will be printed |
| 661 | in any particular order, so a test like |
| 662 | |
| 663 | % Hey! What happened to Monty Python examples? |
Tim Peters | f0768c8 | 2001-02-20 10:57:30 +0000 | [diff] [blame] | 664 | % Tim: ask Guido -- it's his example! |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 665 | \begin{verbatim} |
Fred Drake | 19f3c52 | 2001-02-22 23:15:05 +0000 | [diff] [blame] | 666 | >>> foo() |
| 667 | {"Hermione": "hippogryph", "Harry": "broomstick"} |
| 668 | >>> |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 669 | \end{verbatim} |
| 670 | |
| 671 | is vulnerable! One workaround is to do |
| 672 | |
| 673 | \begin{verbatim} |
Fred Drake | 19f3c52 | 2001-02-22 23:15:05 +0000 | [diff] [blame] | 674 | >>> foo() == {"Hermione": "hippogryph", "Harry": "broomstick"} |
Martin v. Löwis | ccabed3 | 2003-11-27 19:48:03 +0000 | [diff] [blame] | 675 | True |
Fred Drake | 19f3c52 | 2001-02-22 23:15:05 +0000 | [diff] [blame] | 676 | >>> |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 677 | \end{verbatim} |
| 678 | |
| 679 | instead. Another is to do |
| 680 | |
| 681 | \begin{verbatim} |
Fred Drake | 19f3c52 | 2001-02-22 23:15:05 +0000 | [diff] [blame] | 682 | >>> d = foo().items() |
| 683 | >>> d.sort() |
| 684 | >>> d |
| 685 | [('Harry', 'broomstick'), ('Hermione', 'hippogryph')] |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 686 | \end{verbatim} |
| 687 | |
| 688 | There are others, but you get the idea. |
| 689 | |
| 690 | Another bad idea is to print things that embed an object address, like |
| 691 | |
| 692 | \begin{verbatim} |
Fred Drake | 19f3c52 | 2001-02-22 23:15:05 +0000 | [diff] [blame] | 693 | >>> id(1.0) # certain to fail some of the time |
| 694 | 7948648 |
| 695 | >>> |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 696 | \end{verbatim} |
| 697 | |
| 698 | Floating-point numbers are also subject to small output variations across |
| 699 | platforms, because Python defers to the platform C library for float |
| 700 | formatting, and C libraries vary widely in quality here. |
| 701 | |
| 702 | \begin{verbatim} |
Fred Drake | 19f3c52 | 2001-02-22 23:15:05 +0000 | [diff] [blame] | 703 | >>> 1./7 # risky |
| 704 | 0.14285714285714285 |
| 705 | >>> print 1./7 # safer |
| 706 | 0.142857142857 |
| 707 | >>> print round(1./7, 6) # much safer |
| 708 | 0.142857 |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 709 | \end{verbatim} |
| 710 | |
| 711 | Numbers of the form \code{I/2.**J} are safe across all platforms, and I |
| 712 | often contrive doctest examples to produce numbers of that form: |
| 713 | |
| 714 | \begin{verbatim} |
Fred Drake | 19f3c52 | 2001-02-22 23:15:05 +0000 | [diff] [blame] | 715 | >>> 3./4 # utterly safe |
| 716 | 0.75 |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 717 | \end{verbatim} |
| 718 | |
| 719 | Simple fractions are also easier for people to understand, and that makes |
| 720 | for better documentation. |
| 721 | |
Skip Montanaro | 1dc98c4 | 2001-06-08 14:40:28 +0000 | [diff] [blame] | 722 | \item Be careful if you have code that must only execute once. |
| 723 | |
| 724 | If you have module-level code that must only execute once, a more foolproof |
Fred Drake | c115835 | 2001-06-11 14:55:01 +0000 | [diff] [blame] | 725 | definition of \function{_test()} is |
Skip Montanaro | 1dc98c4 | 2001-06-08 14:40:28 +0000 | [diff] [blame] | 726 | |
| 727 | \begin{verbatim} |
| 728 | def _test(): |
| 729 | import doctest, sys |
Martin v. Löwis | 4581cfa | 2002-11-22 08:23:09 +0000 | [diff] [blame] | 730 | doctest.testmod() |
Skip Montanaro | 1dc98c4 | 2001-06-08 14:40:28 +0000 | [diff] [blame] | 731 | \end{verbatim} |
Tim Peters | 6ebe61f | 2003-06-27 20:48:05 +0000 | [diff] [blame] | 732 | |
| 733 | \item WYSIWYG isn't always the case, starting in Python 2.3. The |
Fred Drake | 5d2f515 | 2003-06-28 03:09:06 +0000 | [diff] [blame] | 734 | string form of boolean results changed from \code{'0'} and |
| 735 | \code{'1'} to \code{'False'} and \code{'True'} in Python 2.3. |
Tim Peters | 6ebe61f | 2003-06-27 20:48:05 +0000 | [diff] [blame] | 736 | This makes it clumsy to write a doctest showing boolean results that |
| 737 | passes under multiple versions of Python. In Python 2.3, by default, |
| 738 | and as a special case, if an expected output block consists solely |
Fred Drake | 5d2f515 | 2003-06-28 03:09:06 +0000 | [diff] [blame] | 739 | of \code{'0'} and the actual output block consists solely of |
| 740 | \code{'False'}, that's accepted as an exact match, and similarly for |
| 741 | \code{'1'} versus \code{'True'}. This behavior can be turned off by |
Tim Peters | 6ebe61f | 2003-06-27 20:48:05 +0000 | [diff] [blame] | 742 | passing the new (in 2.3) module constant |
| 743 | \constant{DONT_ACCEPT_TRUE_FOR_1} as the value of \function{testmod()}'s |
| 744 | new (in 2.3) optional \var{optionflags} argument. Some years after |
| 745 | the integer spellings of booleans are history, this hack will |
| 746 | probably be removed again. |
| 747 | |
Fred Drake | c115835 | 2001-06-11 14:55:01 +0000 | [diff] [blame] | 748 | \end{enumerate} |
| 749 | |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 750 | |
| 751 | \subsection{Soapbox} |
| 752 | |
Fred Drake | 7a6b4f0 | 2003-07-17 16:00:01 +0000 | [diff] [blame] | 753 | The first word in ``doctest'' is ``doc,'' and that's why the author |
| 754 | wrote \refmodule{doctest}: to keep documentation up to date. It so |
| 755 | happens that \refmodule{doctest} makes a pleasant unit testing |
| 756 | environment, but that's not its primary purpose. |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 757 | |
Fred Drake | 7a6b4f0 | 2003-07-17 16:00:01 +0000 | [diff] [blame] | 758 | Choose docstring examples with care. There's an art to this that |
| 759 | needs to be learned---it may not be natural at first. Examples should |
| 760 | add genuine value to the documentation. A good example can often be |
| 761 | worth many words. If possible, show just a few normal cases, show |
| 762 | endcases, show interesting subtle cases, and show an example of each |
| 763 | kind of exception that can be raised. You're probably testing for |
| 764 | endcases and subtle cases anyway in an interactive shell: |
| 765 | \refmodule{doctest} wants to make it as easy as possible to capture |
| 766 | those sessions, and will verify they continue to work as designed |
| 767 | forever after. |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 768 | |
Fred Drake | 7a6b4f0 | 2003-07-17 16:00:01 +0000 | [diff] [blame] | 769 | If done with care, the examples will be invaluable for your users, and |
| 770 | will pay back the time it takes to collect them many times over as the |
| 771 | years go by and things change. I'm still amazed at how often one of |
| 772 | my \refmodule{doctest} examples stops working after a ``harmless'' |
| 773 | change. |
Tim Peters | 7688229 | 2001-02-17 05:58:44 +0000 | [diff] [blame] | 774 | |
| 775 | For exhaustive testing, or testing boring cases that add no value to the |
Fred Drake | 7eb1463 | 2001-02-17 17:32:41 +0000 | [diff] [blame] | 776 | docs, define a \code{__test__} dict instead. That's what it's for. |