summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorRobert Collins <robertc@robertcollins.net>2009-07-13 18:22:13 +1000
committerRobert Collins <robertc@robertcollins.net>2009-07-13 18:22:13 +1000
commit0a382afb58f61296ce5a34ba911eaeecd8bdc02c (patch)
tree93da0f31c2dbc5dcb895ea5c04e5c3be1fe2c216 /README
parentac557b5c20ac3c0d60cbfd9682ccc70594a7db28 (diff)
downloadtestresources-0a382afb58f61296ce5a34ba911eaeecd8bdc02c.tar.gz
Really fix bug 284125 by using inspect to look up the TestResult being used and audit activity via the result object tests are being run with.
Diffstat (limited to 'README')
-rw-r--r--README10
1 files changed, 9 insertions, 1 deletions
diff --git a/README b/README
index d47c586..cb6437d 100644
--- a/README
+++ b/README
@@ -36,7 +36,7 @@ can use testresources in your own app without using testtools.
How testresources works:
========================
-There are three main components to make testresources work:
+These are the main components to make testresources work:
1) testresources.TestResource
@@ -106,3 +106,11 @@ during tearDown().
4) testresources.TestLoader
This is a trivial TestLoader that creates OptimisingTestSuites by default.
+
+5) unittest.TestResult
+
+testresources will log activity about resource creation and destruction to the
+result object tests are run with. 4 extension methods are looked for:
+``startCleanResource``, ``stopCleanResource``, ``startMakeResource``,
+``stopMakeResource``. ``testresources.tests.ResultWithResourceExtensions`` is
+an example of a ``TestResult`` with these methods present.