|
6
by mbp at sourcefrog
import all docs from arch |
1 |
*********************** |
2 |
Test plan for Patchflow |
|
3 |
*********************** |
|
4 |
||
5 |
This should be amenable to good automated testing. Here are some |
|
6 |
ideas. |
|
7 |
||
8 |
* Corrupt the branch in various ways and make sure it is detected. |
|
9 |
||
10 |
- To start with test all cases checked by check() |
|
11 |
||
12 |
* Commit. |
|
13 |
||
14 |
||
15 |
I'm using doctest_ for some API tests, and it looks pretty nice. It |
|
16 |
adds some documentation of the pre/post-conditions of various |
|
17 |
operations. It also encourages creating a clean and friendly Python |
|
18 |
API. |
|
19 |
||
20 |
Testing through the Python API does not cover all of the external |
|
21 |
shell interface, but it is much easier to write, because we don't need |
|
22 |
to deal with serializing everything to/from text. |
|
23 |
||
24 |
We may need additional tests to this. |
|
25 |
||
26 |
||
27 |
.. _doctest: http://docs.python.org/lib/module-doctest.html |