summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNed Batchelder <ned@nedbatchelder.com>2016-11-26 08:16:56 -0500
committerNed Batchelder <ned@nedbatchelder.com>2016-11-26 08:16:56 -0500
commite05a8b81ce137bf5335fa3496cbee955e0ad4750 (patch)
tree35ef959e5af835a3262c6a3c212584d9d412b04d
parenta3f308eb21c218ee9a577bce5db29e4548d17e38 (diff)
downloadpython-coveragepy-e05a8b81ce137bf5335fa3496cbee955e0ad4750.tar.gz
Change nose example to pytest example. #521
-rw-r--r--doc/index.rst9
1 files changed, 5 insertions, 4 deletions
diff --git a/doc/index.rst b/doc/index.rst
index 25fd1bc..07e940f 100644
--- a/doc/index.rst
+++ b/doc/index.rst
@@ -145,14 +145,15 @@ If you need more control over how your project is measured, you can use the
:ref:`API <api>`.
Some test runners provide coverage integration to make it easy to use
-coverage.py while running tests. For example, `nose`_ has a `cover plug-in`_.
+coverage.py while running tests. For example, `pytest`_ has the `pytest-cov`_
+plugin.
You can fine-tune coverage.py's view of your code by directing it to ignore
parts that you know aren't interesting. See :ref:`source` and :ref:`excluding`
for details.
-.. _nose: http://nose.readthedocs.io
-.. _cover plug-in: https://nose.readthedocs.io/en/latest/plugins/cover.html
+.. _pytest: http://doc.pytest.org
+.. _pytest-cov: http://pytest-cov.readthedocs.io
.. _contact:
@@ -176,7 +177,7 @@ GitHub.
`I can be reached`_ in a number of ways. I'm happy to answer questions about
using coverage.py.
-.. _I can be reached: http://nedbatchelder.com/site/aboutned.html
+.. _I can be reached: http://nedbatchelder.com/site/aboutned.html