diff options
| author | deisner <deisner@gmail.com> | 2014-10-06 17:01:40 -0400 |
|---|---|---|
| committer | Steve Piercy <web@stevepiercy.com> | 2014-10-07 00:00:51 -0700 |
| commit | c92f49b63f005a63a0d9ac33973e7cec84b07c55 (patch) | |
| tree | 7a4646b4dc66f71580d06191f49c1c9d7d71c703 | |
| parent | 159105a203dc62ef6306fb3537caab42bca0df8e (diff) | |
| download | pyramid-c92f49b63f005a63a0d9ac33973e7cec84b07c55.tar.gz pyramid-c92f49b63f005a63a0d9ac33973e7cec84b07c55.tar.bz2 pyramid-c92f49b63f005a63a0d9ac33973e7cec84b07c55.zip | |
Update functional_testing.rst
Make it clear that the tests.py file in the functional_testing directory is the one to edit. Also, warn about a potential "gotcha": if the tests.py file is executable, it will be silently ignored. (I ran into this problem while going through the tutorial. This can happen if the file is being edited on a network file share from a different OS, for example.).
| -rw-r--r-- | docs/quick_tutorial/functional_testing.rst | 6 |
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''``? |