~ubuntuone-hackers/ols-tests/trunk

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
53
54
* find a way to keep a TextTestResult for feedback while still creating a
  subunit file for later processing.

* refactor Loader to use Walker.

* enhance RunTestsArgParser for subclassing

 - don't force common options to daughter classes that may not care about
   them (--module, --pick or --format for example)

  - make TestResult formats pluggable

* review the ols-run-tests option names

   Those options give access to several and clearly distinct parts which
   should be reflected in their names:

   '--load-module' vs '--module
   '--load-file' or '--load-list' vs '--load'
   '--filter-{in,ex}clude' vs --{in,ex}clude
   '--result-format' vs '--format'
   '--run-concurrency' vs '--concurrency'
   '--run-list-only' vs '--list'
   
* support subunit tags ?

   Tags use cases are a bit unclear, parametrization and proper use of
   features seem to already provide a bunch of ways to characterize tests.

* finish setup.py

  Missing:

  - tests

    ./setup.py check
    ./setup.py --name

  - requirements

  - description

  - platform

* documentation

   Examples (at least pointing to the significant tests)
   BYOR (Build Your Own Runner)

* README

   The actual README content should be turned in a proper doc and replaced
   with a description of the sources and how they are managed (releases,
   packaging, running tests).