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.).
| | |
| | | $ $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 |
| | |
| | | Extra Credit |
| | | ============ |
| | | |
| | | #. Why do our functional tests use ``b''``? |
| | | #. Why do our functional tests use ``b''``? |