diff options
| author | Ned Batchelder <ned@nedbatchelder.com> | 2009-09-13 09:14:39 -0400 |
|---|---|---|
| committer | Ned Batchelder <ned@nedbatchelder.com> | 2009-09-13 09:14:39 -0400 |
| commit | efb726425ff168b04de2063fa23886af5a515c88 (patch) | |
| tree | 04d7d681267ca9bfee22091750c924e1b2101734 /doc/faq.rst | |
| parent | 44b9351f801018d76230914db956b404940f8461 (diff) | |
| download | python-coveragepy-efb726425ff168b04de2063fa23886af5a515c88.tar.gz | |
Docs updated for the new command-line syntax.
Diffstat (limited to 'doc/faq.rst')
| -rw-r--r-- | doc/faq.rst | 9 |
1 files changed, 7 insertions, 2 deletions
diff --git a/doc/faq.rst b/doc/faq.rst index d1b4160..385f1fe 100644 --- a/doc/faq.rst +++ b/doc/faq.rst @@ -9,6 +9,7 @@ FAQ and other help Frequently asked questions -------------------------- + **Q: Why do unexecutable lines show up as executed?** Usually this is because you've updated your code and run coverage on it @@ -16,8 +17,10 @@ again without erasing the old data. Coverage records line numbers executed, so the old data may have recorded a line number which has since moved, causing coverage to claim a line has been executed which cannot be. -Use the -e switch on the command line to erase all data before starting the next -run. +If you are using the ``-x`` command line action, it doesn't erase first by +default. Switch to the ``coverage run`` command, or use the ``-e`` switch to +erase all data before starting the next run. + **Q: Why do the bodies of functions (or classes) show as executed, but the def lines do not?** @@ -32,10 +35,12 @@ to run your program with coverage, then your entire program will be monitored. If you are using the :ref:`API <api>`, you need to call coverage.start() before importing the modules that define your functions. + **Q: Does coverage work on Python 3.x?** Not yet, but that's next on my list. + **Q: Isn't coverage testing the best thing ever?** It's good, but `it isn't perfect |