diff options
author | Robert Collins <robertc@robertcollins.net> | 2009-06-17 19:11:03 +1000 |
---|---|---|
committer | Robert Collins <robertc@robertcollins.net> | 2009-06-17 19:11:03 +1000 |
commit | b571a618c617fb02805731eab238baa75c5a4179 (patch) | |
tree | ee118fc2ce35a14d46e2c6852ec73e66286929a5 /README | |
parent | 517ce1f70cb7a969b808a0445dd75c278f61ff69 (diff) | |
parent | 58b817afeb8b95e35d5a6347266316b9f35a3465 (diff) | |
download | testresources-b571a618c617fb02805731eab238baa75c5a4179.tar.gz |
Merge adsorbSuite->addTests rename.
Diffstat (limited to 'README')
-rw-r--r-- | README | 8 |
1 files changed, 5 insertions, 3 deletions
@@ -73,9 +73,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 |