On Jan 22, 9:08 pm, "Edward K. Ream" <[email protected]> wrote: > On Fri, Jan 22, 2010 at 11:18 AM, zpcspm <[email protected]> wrote: > > I'm trying to write a simple test that I'm running by selecting it and > > then typing 'run-unit-tests-locally'. > > Did you notice that the code works when run with the execute-script > command? That indicates that something strange is going on related to > unit testing. > > To make things easier to see, I added a call to p1.expand() after the line: > p1 = p.insertAsLastChild() > > There is no reason at all to get stuck :-) Just insert a call to > g.pdb() in pasteOutline(). Compare what happens when run with ctrl-b > vs. run-unit-tests-locally. You will see that in the latter case > readSaxFile misses the body text. > > So it looks like a bug which I'll fix soon. > > Edward
Ok. Feel free to complete my example test with a couple of asserts that compare the headlines and bodies of these two created children of root and add it to the leo unit tests. Since you cleared the things up and this seems to be a leo bug rather than me doing something wrong, it'll be good to have a simple regression test for this. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
