From 8c56ae41b6f0221d72f1a255ce1a3ac467b98d79 Mon Sep 17 00:00:00 2001 From: Chris McDonough Date: Sun, 27 Dec 2009 22:47:08 +0000 Subject: - Added manual index entries to generated index. --- docs/narr/unittesting.rst | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) (limited to 'docs/narr/unittesting.rst') diff --git a/docs/narr/unittesting.rst b/docs/narr/unittesting.rst index 316142c08..d032e3a36 100644 --- a/docs/narr/unittesting.rst +++ b/docs/narr/unittesting.rst @@ -1,3 +1,7 @@ +.. index:: + single: unit testing + single: integration testing + .. _unittesting_chapter: Unit and Integration Testing @@ -51,6 +55,11 @@ integration tests easier to write. The facilities become particularly useful when your code calls into :mod:`repoze.bfg` -related framework functions. +.. index:: + pair: test; setup + pair: test; tear down + single: unittest + .. _test_setup_and_teardown: Test Set Up and Tear Down @@ -151,6 +160,10 @@ method within the ``setUp`` of a unit test, then subsequently call its anything if the application you're testing does not call any ``get_current*`` function. +.. index:: + single: repoze.bfg.testing + pair: Configurator; testing + Using the ``Configurator`` and ``repoze.bfg.testing`` APIs in Unit Tests ------------------------------------------------------------------------ @@ -282,6 +295,9 @@ representing "dummy" implementations of a request and a model. See also the various methods of the :term:`Configurator` documented in :ref:`configuration_module` that begin with the ``testing_`` prefix. +.. index:: + pair: creating; integration tests + .. _integration_tests: Creating Integration Tests -- cgit v1.2.3