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 | 38b5b2f6e3b152f4073fee90e5684cf890184660 (patch) | |
| tree | 3edde069715e1084ca55372452445e87a70287a5 /doc/faq.rst | |
| parent | 5979544c1cf0115c11555239d1da20add04c34ec (diff) | |
| download | python-coveragepy-git-38b5b2f6e3b152f4073fee90e5684cf890184660.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 d1b41609..385f1fec 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 |