From 7200877071d957ff3eecb0c7eaefb03ce3ea8f86 Mon Sep 17 00:00:00 2001 From: Jonathan Lange Date: Wed, 27 Jan 2010 08:42:31 +0000 Subject: Some spelling corrections. --- README | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/README b/README index 215a10f..62bda6f 100644 --- a/README +++ b/README @@ -60,18 +60,18 @@ By extending or mixing-in this class, tests can have necessary resources automatically allocated and disposed or recycled. ResourceTestCase can be used as a base class for tests, and when that is done -tests will have their ``resources`` attribute automatically checked for resources -by both OptimisingTestSuite and their own setUp() and tearDown() methods. -(This allows tests to remain functional without needing this specific -TestSuite as a container). Alternatively, you can call -ResourceTestCase.setUpResources(self) and -ResourceTestCase.tearDownResources(self) from your own classes setUp and -tearDown and the same behaviour will be activated. +tests will have their ``resources`` attribute automatically checked for +resources by both OptimisingTestSuite and their own setUp() and tearDown() +methods. (This allows tests to remain functional without needing this specific +TestSuite as a container). Alternatively, you can call setUpResources(self, +resources, test_result) and tearDownResources(self, resources, test_result) +from your own classes setUp and tearDown and the same behaviour will be +activated. To declare the use of a resource, set the ``resources`` attribute to a list of tuples of ``(attribute_name, resource_factory)``. -During setUp, for each declared requriment, the test gains an attribute +During setUp, for each declared requirement, the test gains an attribute pointing to an allocated resource, which is the result of calling ``resource_factory.getResource()``. ``finishedWith`` will be called on each resource during tearDown(). -- cgit v1.2.1