diff options
| author | Ned Batchelder <ned@nedbatchelder.com> | 2009-10-04 17:32:39 -0400 |
|---|---|---|
| committer | Ned Batchelder <ned@nedbatchelder.com> | 2009-10-04 17:32:39 -0400 |
| commit | 610eb85f1885a43c3331437dc8c88da388739c22 (patch) | |
| tree | c942012c0d7d46e005d343eff1fc90762bd45da5 /doc/faq.rst | |
| parent | 7f13ce4730fd989d21b966ce4bcc86a45ae3a486 (diff) | |
| download | python-coveragepy-git-610eb85f1885a43c3331437dc8c88da388739c22.tar.gz | |
Documentation polishing for a 3.1 release.
Diffstat (limited to 'doc/faq.rst')
| -rw-r--r-- | doc/faq.rst | 14 |
1 files changed, 12 insertions, 2 deletions
diff --git a/doc/faq.rst b/doc/faq.rst index 385f1fec..6b8e7fa7 100644 --- a/doc/faq.rst +++ b/doc/faq.rst @@ -10,6 +10,16 @@ Frequently asked questions -------------------------- +**Q: I use `nose`_ to run my tests, and the ``--with-cover`` plugin doesn't let +me create HTML or XML reports. What should I do? + +.. _nose: http://somethingaboutorange.com/mrl/projects/nose + +First run your tests and collect coverage data with nose and its plugin. This +will write coverage data into a .coverage file. Then run coverage.py from the +command line to create the reports you need from that data. + + **Q: Why do unexecutable lines show up as executed?** Usually this is because you've updated your code and run coverage on it @@ -36,9 +46,9 @@ 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?** +**Q: Does coverage.py work on Python 3.x?** -Not yet, but that's next on my list. +Yes, as of coverage.py 3.1, Python 3.1 is supported. **Q: Isn't coverage testing the best thing ever?** |