diff options
author | Jonathan Lange <jml@canonical.com> | 2008-09-13 21:48:04 +1000 |
---|---|---|
committer | Jonathan Lange <jml@canonical.com> | 2008-09-13 21:48:04 +1000 |
commit | 92d8a30ff90511b63d265400c3c70e53a95e4d41 (patch) | |
tree | d09a014c28a3bd43874d3fb532481cc24ab962b6 /TODO | |
parent | 626ddc2cc539d3ac8f82e5112da69e18160836cb (diff) | |
download | testresources-git-92d8a30ff90511b63d265400c3c70e53a95e4d41.tar.gz |
Update NEWS and TODO for adsorbSuite change.
Diffstat (limited to 'TODO')
-rw-r--r-- | TODO | 24 |
1 files changed, 0 insertions, 24 deletions
@@ -68,30 +68,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', |