diff options
| author | Jonathan Lange <jml@canonical.com> | 2008-09-13 21:55:30 +1000 |
|---|---|---|
| committer | Jonathan Lange <jml@canonical.com> | 2008-09-13 21:55:30 +1000 |
| commit | 4a4e6d8c79b4d5be72ae3b0b750d8364ba3873c7 (patch) | |
| tree | 01ec9900a1e9396d640bcece6f11fb97f473ae89 | |
| parent | 92d8a30ff90511b63d265400c3c70e53a95e4d41 (diff) | |
| download | testresources-git-4a4e6d8c79b4d5be72ae3b0b750d8364ba3873c7.tar.gz | |
Update README.
| -rw-r--r-- | README | 8 |
1 files changed, 5 insertions, 3 deletions
@@ -67,9 +67,11 @@ minimise the number of setup and tear downs required. It attempts to achieve this by callling getResource() and finishedWith() around the sequence of tests that use a specific resource. -OptimisingTestSuite has a new method over normal TestSuites: -adsorbSuite(test_case_or_suite), which scans another test suite and -incorporates all of its tests directly into the OptimisingTestSuite. +Tests are added to an OptimisingTestSuite as normal. Any standard library +TestSuite objects will be flattened, while any custom TestSuite subclasses +will be distributed across their member tests. This means that any custom +logic in test suites should be preserved, at the price of some level of +optimisation. Because the test suite does the optimisation, you can control the amount of optimising that takes place by adding more or fewer tests to a single |