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

Mention the TESTING flag in the docs

Browse source
This commit is contained in:
Armin Ronacher 2011-06-17 21:53:11 +02:00
parent d62e277dfe
commit 7e55b5084d
2 changed files with 23 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

24
docs/testing.rst
View file

@ -41,6 +41,7 @@ In order to test the application, we add a second module
def setUp(self): def setUp(self):
self.db_fd, flaskr.app.config['DATABASE'] = tempfile.mkstemp() self.db_fd, flaskr.app.config['DATABASE'] = tempfile.mkstemp()
flaskr.app.config['TESTING'] = True
self.app = flaskr.app.test_client() self.app = flaskr.app.test_client()
flaskr.init_db() flaskr.init_db()
@ -55,7 +56,10 @@ The code in the :meth:`~unittest.TestCase.setUp` method creates a new test
client and initializes a new database. This function is called before client and initializes a new database. This function is called before
each individual test function is run. To delete the database after the each individual test function is run. To delete the database after the
test, we close the file and remove it from the filesystem in the test, we close the file and remove it from the filesystem in the
:meth:`~unittest.TestCase.tearDown` method. :meth:`~unittest.TestCase.tearDown` method. Additionally during setup the
``TESTING`` config flag is activated. What it does is disabling the error
catching during request handling so that you get better error reports when
performing test requests against the application.
This test client will give us a simple interface to the application. We can This test client will give us a simple interface to the application. We can
trigger test requests to the application, and the client will also keep track trigger test requests to the application, and the client will also keep track
@ -215,6 +219,23 @@ If you want to test your application with different configurations and
there does not seem to be a good way to do that, consider switching to there does not seem to be a good way to do that, consider switching to
application factories (see :ref:`app-factories`). application factories (see :ref:`app-factories`).
Note however that if you are using a test request context, the
:meth:`~flask.Flask.before_request` functions are not automatically called
same fore :meth:`~flask.Flask.after_request` functions. However
:meth:`~flask.Flask.teardown_request` functions are indeed executed when
the test request context leaves the `with` block. If you do want the
:meth:`~flask.Flask.before_request` functions to be called as well, you
need to call :meth:`~flask.Flask.preprocess_request` yourself::
app = flask.Flask(__name__)
with app.test_request_context('/?name=Peter'):
app.preprocess_request()
...
This can be necessary to open database connections or something similar
depending on how your application was designed.
Keeping the Context Around Keeping the Context Around
-------------------------- --------------------------
@ -238,4 +259,3 @@ is no longer available (because you are trying to use it outside of the actual r
However, keep in mind that any :meth:`~flask.Flask.after_request` functions However, keep in mind that any :meth:`~flask.Flask.after_request` functions
are already called at this point so your database connection and are already called at this point so your database connection and
everything involved is probably already closed down. everything involved is probably already closed down.

1
examples/flaskr/flaskr_tests.py
View file

@ -19,6 +19,7 @@ class FlaskrTestCase(unittest.TestCase):
def setUp(self): def setUp(self):
"""Before each test, set up a blank database""" """Before each test, set up a blank database"""
self.db_fd, flaskr.app.config['DATABASE'] = tempfile.mkstemp() self.db_fd, flaskr.app.config['DATABASE'] = tempfile.mkstemp()
flaskr.app.config['TESTING'] = True
self.app = flaskr.app.test_client() self.app = flaskr.app.test_client()
flaskr.init_db() flaskr.init_db()