maya-chen/flask
1
0
Fork 0
forked from orbit-oss/flask
Code Pull requests Activity

Minor testing documentation fixes (grammar, etc)

Browse source
This commit is contained in:
Adam Zapletal 2010-06-28 11:24:37 +08:00 • committed by Armin Ronacher
parent 5ede53066f
commit 505c530c9a
1 changed files with 6 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

12
docs/testing.rst
View file

@ -8,8 +8,8 @@ Testing Flask Applications
Not sure where that is coming from, and it's not entirely correct, but Not sure where that is coming from, and it's not entirely correct, but
also not that far from the truth. Untested applications make it hard to also not that far from the truth. Untested applications make it hard to
improve existing code and developers of untested applications tend to improve existing code and developers of untested applications tend to
become pretty paranoid. If an application however has automated tests, you become pretty paranoid. If an application has automated tests, you can
can safely change things and you will instantly know if your change broke safely change things, and you will instantly know if your change broke
something. something.
Flask gives you a couple of ways to test applications. It mainly does Flask gives you a couple of ways to test applications. It mainly does
@ -60,7 +60,7 @@ each individual test function. To delete the database after the test, we
close the file and remove it from the filesystem in the close the file and remove it from the filesystem in the
:meth:`~unittest.TestCase.tearDown` method. What the test client does is :meth:`~unittest.TestCase.tearDown` method. What the test client does is
give us a simple interface to the application. We can trigger test give us a simple interface to the application. We can trigger test
requests to the application and the client will also keep track of cookies requests to the application, and the client will also keep track of cookies
for us. for us.
Because SQLite3 is filesystem-based we can easily use the tempfile module Because SQLite3 is filesystem-based we can easily use the tempfile module
@ -130,7 +130,7 @@ Logging In and Out
------------------ ------------------
The majority of the functionality of our application is only available for The majority of the functionality of our application is only available for
the administration user. So we need a way to log our test client in to the the administrative user, so we need a way to log our test client in to the
application and out of it again. For that we fire some requests to the application and out of it again. For that we fire some requests to the
login and logout pages with the required form data (username and login and logout pages with the required form data (username and
password). Because the login and logout pages redirect, we tell the password). Because the login and logout pages redirect, we tell the
@ -200,12 +200,12 @@ suite.
Other Testing Tricks Other Testing Tricks
-------------------- --------------------
Besides using the test client we used above there is also the Besides using the test client we used above, there is also the
:meth:`~flask.Flask.test_request_context` method that in combination with :meth:`~flask.Flask.test_request_context` method that in combination with
the `with` statement can be used to activate a request context the `with` statement can be used to activate a request context
temporarily. With that you can access the :class:`~flask.request`, temporarily. With that you can access the :class:`~flask.request`,
:class:`~flask.g` and :class:`~flask.session` objects like in view :class:`~flask.g` and :class:`~flask.session` objects like in view
functions. Here a full example that showcases this:: functions. Here's a full example that showcases this::
app = flask.Flask(__name__) app = flask.Flask(__name__)