diff options
| author | Carlos de la Guardia <cguardia@yahoo.com> | 2010-03-23 17:32:15 +0000 |
|---|---|---|
| committer | Carlos de la Guardia <cguardia@yahoo.com> | 2010-03-23 17:32:15 +0000 |
| commit | 8b154d39e9f6acf6b98b89b03e0bf7f86889f5a3 (patch) | |
| tree | 83c15e7a5118a6902116730a54f5709eb1532262 /docs | |
| parent | d9e815bc724234cddfb6b3d8dc6479717d3c96aa (diff) | |
| download | pyramid-8b154d39e9f6acf6b98b89b03e0bf7f86889f5a3.tar.gz pyramid-8b154d39e9f6acf6b98b89b03e0bf7f86889f5a3.tar.bz2 pyramid-8b154d39e9f6acf6b98b89b03e0bf7f86889f5a3.zip | |
one missing and one extra letters
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/narr/unittesting.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/narr/unittesting.rst b/docs/narr/unittesting.rst index a13f90952..4ca64eb9d 100644 --- a/docs/narr/unittesting.rst +++ b/docs/narr/unittesting.rst @@ -77,14 +77,14 @@ these functions and the data structures they return. If your code uses these ``get_current_*`` functions or calls :mod:`repoze.bfg` code which uses ``get_current_*`` functions, you -will need to construct at :term:`Configurator` and call its ``begin`` +will need to construct a :term:`Configurator` and call its ``begin`` method within the ``setUp`` method of your unit test and call the same configurator's ``end`` method within the ``tearDown`` method of your unit test. The use of a Configurator and its ``begin`` and ``end`` methods allows you to supply each unit test method in a test case with an environment -that has a isolated registry and an isolated request for the duration +that has an isolated registry and an isolated request for the duration of a single test. Here's an example of using this feature: .. code-block:: python |
