[Checkins] SVN: Sandbox/ulif/z3c-testsetup/trunk/src/z3c/testsetup/pythontestsetup.txt Mode docs/tests.

[Uli Fouquet]

Log message for revision 83802:
  Mode docs/tests.

Changed:
  U   Sandbox/ulif/z3c-testsetup/trunk/src/z3c/testsetup/pythontestsetup.txt

-=-
Modified: Sandbox/ulif/z3c-testsetup/trunk/src/z3c/testsetup/pythontestsetup.txt
===================================================================
--- Sandbox/ulif/z3c-testsetup/trunk/src/z3c/testsetup/pythontestsetup.txt	2008-02-13 16:04:35 UTC (rev 83801)
+++ Sandbox/ulif/z3c-testsetup/trunk/src/z3c/testsetup/pythontestsetup.txt	2008-02-13 18:51:34 UTC (rev 83802)
@@ -149,6 +149,10 @@
 modules are registered, but not **how** they are registered. This is
 not the case for doctest setups.
 
+The customization can be done by setting the appropriate attributes or
+functions of a ``UnitTestSetup`` instance, or by passing appropriate
+values to the constructor. Both methods will be shown below.
+
 Customizing the module search:
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -226,6 +230,17 @@
 one regular expression that matches each of the possible terms but no
 others.
 
+The same effect can be archieved by passing the ``regexp_list``
+keyword parameter to the constructor::
+
+    >>> custom_setup = UnitTestSetup(cave,
+    ...  regexp_list= ['^\\s*:(T|t)est-(L|l)ayer:\\s*(F|false)\\s*'])
+    >>> suite = custom_setup.getTestSuite()
+    >>> get_basenames_from_suite(suite)
+    ['notatest2.py']
+
+
+
 If you need more complex checks here, you can derive your customized
 test setup class and overwrite ``isModule()``.