summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorOladipo Odumosu <dodumosu@timbaobjects.com>2016-11-16 05:12:01 +0100
committerMichael Merickel <michael@merickel.org>2016-11-15 22:57:25 -0600
commit371d1115aed2e0f99948e09d06e96e7ba4846609 (patch)
tree351a71e86b9412632d2410181c6875c58a908c56
parent4db295a08c931328fa6bc0d15c7b9aa57ddad86c (diff)
downloadpyramid-371d1115aed2e0f99948e09d06e96e7ba4846609.tar.gz
pyramid-371d1115aed2e0f99948e09d06e96e7ba4846609.tar.bz2
pyramid-371d1115aed2e0f99948e09d06e96e7ba4846609.zip
The updated pyramid-jinja2 scaffold already sets up test requirments in `setup.py`
-rw-r--r--docs/quick_tour.rst10
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/quick_tour.rst b/docs/quick_tour.rst
index 451830687..47fdb0a88 100644
--- a/docs/quick_tour.rst
+++ b/docs/quick_tour.rst
@@ -678,10 +678,10 @@ egregious, as Pyramid has had a deep commitment to full test coverage since
before its release.
Our ``pyramid_jinja2_starter`` scaffold generated a ``tests.py`` module with
-one unit test in it. To run it, let's install the handy ``pytest`` test runner
-by editing ``setup.py``. While we're at it, we'll throw in the ``pytest-cov``
-tool which yells at us for code that isn't tested. Insert and edit the
-following lines as shown:
+one unit test in it. It also setup ``setup.py`` with test requirements:
+``py.test`` as the test runner, ``WebTest`` for running view tests, and the
+``pytest-cov`` tool which yells at us for code that isn't tested. The
+highlighted lines show this:
.. code-block:: python
:linenos:
@@ -711,7 +711,7 @@ following lines as shown:
'testing': tests_require,
},
-We changed ``setup.py`` which means we need to rerun ``$VENV/bin/pip install -e
+To install the test requirements, run ``$VENV/bin/pip install -e
".[testing]"``. We can now run all our tests:
.. code-block:: bash