summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authoramatellanes <dev.amatellanes@gmail.com>2014-06-24 23:09:45 +0200
committeramatellanes <dev.amatellanes@gmail.com>2014-06-24 23:09:45 +0200
commit8062b8de265f96cd048e0443b885681cd4f016fa (patch)
treef4d72490c3404be43d7f65e31ce4f73c6d2c7db5
parent71b5ee2161289f56318308f070fb9e91fa6017b1 (diff)
downloadnose-8062b8de265f96cd048e0443b885681cd4f016fa.tar.gz
Fix Testid docs
-rw-r--r--nose/plugins/testid.py8
1 files changed, 4 insertions, 4 deletions
diff --git a/nose/plugins/testid.py b/nose/plugins/testid.py
index cb7bde6..49fff9b 100644
--- a/nose/plugins/testid.py
+++ b/nose/plugins/testid.py
@@ -16,7 +16,7 @@ When adding ``--with-id`` you'll see::
% nosetests -v --with-id
#1 tests.test_a ... ok
#2 tests.test_b ... ok
- #2 tests.test_c ... ok
+ #3 tests.test_c ... ok
Then you can re-run individual tests by supplying just an id number::
@@ -85,9 +85,9 @@ Second::
.. note ::
If you expect to use ``--failed`` regularly, it's a good idea to always run
- run using the ``--with-id`` option. This will ensure that an id file is
- always created, allowing you to add ``--failed`` to the command line as soon
- as you have failing tests. Otherwise, your first run using ``--failed`` will
+ using the ``--with-id`` option. This will ensure that an id file is always
+ created, allowing you to add ``--failed`` to the command line as soon as
+ you have failing tests. Otherwise, your first run using ``--failed`` will
(perhaps surprisingly) run *all* tests, because there won't be an id file
containing the record of failed tests from your previous run.