File: TODO

package info (click to toggle)
testresources 2.0.1-2
  • links: PTS, VCS
  • area: main
  • in suites: bookworm, bullseye, sid
  • size: 300 kB
  • sloc: python: 1,598; makefile: 22
file content (52 lines) | stat: -rw-r--r-- 1,404 bytes parent folder | download | duplicates (5)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52

Tasks
=====

* Sort out naming & coding convention and write up in tree.

* Test exceptions being raised from make and clean

* More docs.

Questions
=========

* Why does finishedWith take a parameter? Why not use
  TestResource._currentResource?

* How should resources be composed? (Partially answered).

* How can testresources be used with layers?

* How can testresources be used to *replace* layers?


Bugs
====



Ideas
=====

* Have a dumb equivalent of OptimisingTestSuite that doesn't do any sorting.
  Rely on others to do the sorting first.

* Introduce timing hooks for better estimation of setUpCost and tearDownCost.

* Store timing information so that cost estimations can improve over time.

* Change the interface of TestResource so that make and clean are methods on
  some *other* object, rather than methods to be overridden. This object could
  well have the interface .setUp() and .tearDown()!

* Move ResourcedTestCase.setUpResources and tearDownResources to be methods.

* Change ResourcedTestCase.resources to a dict (currently a list of 2-tuples).

* There are now many simple test helpers. These can probably be consolidated.

* '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',
  'liability' or 'fixture'.