31 |
not a Fen as parameter. Consider: if/when we split Swamp out of fenfire, |
not a Fen as parameter. Consider: if/when we split Swamp out of fenfire, |
32 |
RDFUtil should go with that. |
RDFUtil should go with that. |
33 |
|
|
34 |
|
- fix RSTText.test: |
35 |
|
- 1) use org.fenfire.test.fen |
36 |
|
- 2) simplify: |
37 |
|
- do you really need |
38 |
|
dispnodeview = ff.view.DispatchingNodeView(fen.txtfunc, |
39 |
|
textnodeview, |
40 |
|
pagenodeview) |
41 |
|
to make it crash? &c. Pare it down |
42 |
|
- 3) Split the test: |
43 |
|
mainNode.keystroke('Space') |
44 |
|
mainNode.keystroke('Space') |
45 |
|
mainNode.keystroke('Space') |
46 |
|
mainNode.keystroke('Return') |
47 |
|
is bad style: have a first test that does this and asserts things |
48 |
|
about the resulting structure. Then, another test which creates |
49 |
|
the structure by hand in a fresh fen. When you can make *that* |
50 |
|
crash, you're getting along really well. |
51 |
|
|
52 |
|
|
53 |
============= |
============= |
54 |
Past: |
Past: |
55 |
============= |
============= |