On Wed, Nov 9, 2011 at 7:39 AM, mdb <[email protected]> wrote: > OK, did the steps > There are two @test Assert True nodes and I assumed I should ignore > the one in the @ignore branch
Correct. > If I understand right, Alt-4 > (1) only runs unit @test nodes that are marked > (2) sends results to console Correct. > And I originally thought Alt-4 used leoDynamicUnittest.py but by > adding a print statement that I expected to go to the console, I see > it does not. No. Alt-4 (in leoPy.leo) is indeed bound to run-marked-unit-tests-externally, and print, g.trace, etc. work as expected, as I have just verified. Warning: the system is flexible enough that sometimes it can be confusing. When in doubt, do unmark-all, followed by a single Ctrl-m to ensure you are running only the expected unit tests. BTW, there is a small Easter Egg: if you mark a node that is *not* an @test or @suite nodes, all the *descendant* @test or @suite nodes will be considered to be marked for the purposes of the run-marked-unit-test commands. I believe this is the intuitive operation, in fact, so calling it an Easter Egg is a bit misleading. > Not 100% sure of the role of leoProjects.txt. Your working notes? and > not saved test results Correct. Edward -- 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.
