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 /TODO | |
parent | 517ce1f70cb7a969b808a0445dd75c278f61ff69 (diff) | |
parent | 58b817afeb8b95e35d5a6347266316b9f35a3465 (diff) | |
download | testresources-git-b571a618c617fb02805731eab238baa75c5a4179.tar.gz |
Merge adsorbSuite->addTests rename.
Diffstat (limited to 'TODO')
-rw-r--r-- | TODO | 24 |
1 files changed, 0 insertions, 24 deletions
@@ -50,30 +50,6 @@ Ideas * There are now many simple test helpers. These can probably be consolidated. -* We want to support adding other "special" test suites to - OptimisingTestSuite. In particular, if we add a test suite that provides - services to its tests to an OptimisingTestSuite, adsorbSuite should not - totally flatten the suite, but instead keep the suite, even if it changes - the structure of the tests. - - e.g. addTest maintains the structure: - >>> OptimisingTestSuite().addTest(SpecialSuite([a, b]))._tests - [SpecialSuite([a, b])] - - Currently, adsorbSuite destroys all suite structure: - >>> OptimisingTestSuite().adsorbSuite(SpecialSuite([a, b]))._tests - [a, b] - - Instead, it should preserve the suite while changing the structure: - >>> OptimisingTestSuite().adsorbSuite(SpecialSuite([a, b]))._tests - [SpecialSuite(a), SpecialSuite(b)] - - All of the tests in each of the resulting new SpecialSuites should have - identical resource requirements so we can still optimise. - - Once it does this, we should deprecate adsorbSuite and move this - functionality to addTest / addTests. - * 'TestResource' isn't a very good name. Since the switch to instance-based resources, it's even worse, since the objects are more like resource factories or resource managers. Other possible names involve 'asset', |