summaryrefslogtreecommitdiff
path: root/docs/quick_tutorial/functional_testing.rst
diff options
context:
space:
mode:
Diffstat (limited to 'docs/quick_tutorial/functional_testing.rst')
-rw-r--r--docs/quick_tutorial/functional_testing.rst6
1 files changed, 4 insertions, 2 deletions
diff --git a/docs/quick_tutorial/functional_testing.rst b/docs/quick_tutorial/functional_testing.rst
index 205ddf5cb..ddcf6b77d 100644
--- a/docs/quick_tutorial/functional_testing.rst
+++ b/docs/quick_tutorial/functional_testing.rst
@@ -37,12 +37,14 @@ Steps
$ $VENV/bin/python setup.py develop
$ $VENV/bin/easy_install webtest
-#. Let's extend ``unit_testing/tutorial/tests.py`` to include a
+#. Let's extend ``functional_testing/tutorial/tests.py`` to include a
functional test:
.. literalinclude:: functional_testing/tutorial/tests.py
:linenos:
+ Be sure this file is not executable, or ``nosetests`` may not include your tests.
+
#. Now run the tests:
.. code-block:: bash
@@ -67,4 +69,4 @@ execution time of our tests.
Extra Credit
============
-#. Why do our functional tests use ``b''``? \ No newline at end of file
+#. Why do our functional tests use ``b''``?