summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorRobert Collins <robertc@robertcollins.net>2009-03-08 15:37:33 +1100
committerRobert Collins <robertc@robertcollins.net>2009-03-08 15:37:33 +1100
commitf200c2bcf7eaef2dcad37737ebe9fb5e629c938e (patch)
treeffe2cee5823665318151e0a46ccfbe2741ccd3d7 /README
parent50d71aaaf387ad7dc259eb291d2860a0b946fd8c (diff)
downloadtestscenarios-f200c2bcf7eaef2dcad37737ebe9fb5e629c938e.tar.gz
Factor out all the individual components of generate_tests.
Diffstat (limited to 'README')
-rw-r--r--README12
1 files changed, 12 insertions, 0 deletions
diff --git a/README b/README
index d13172a..f18a027 100644
--- a/README
+++ b/README
@@ -189,3 +189,15 @@ For instance::
>>> class TestHashPerformance(TestCase):
>>>
>>> scenarios = hash_scenarios
+
+
+Forcing Scenarios
++++++++++++++++++
+
+The ``apply_scenarios`` function can be useful to apply scenarios to a test
+that has none applied. ``apply_scenarios`` is the workhorse for
+``generate_scenarios``, except it takes the scenarios passed in rather than
+introspecting the test object to determine the scenarios. The
+``apply_scenarios`` function does not reset the test scenarios attribute,
+allowing it to be used to layer scenarios without affecting existing scenario
+selection.