On Oct 31, 11:30 am, "Edward K. Ream" <[email protected]> wrote:
> 3. We want three kinds of (local) unit tests:: > > run-all-unit-tests-locally > run-selected-unit-tests-locally > run-marked-unit-tests-locally The run-marked-unit-tests-locally/externally commands now work with less surprise. A. If a marked node is any kind of test node (@test, @suite or hidden test), then it is added to the list of tests to be run, as always. B. If a marked node is *not* any kind of test node, all *descendent* tests nodes are added to the list of tests to be run. I discovered that this is needed by accident, and it's a good addition. BTW, It was not possible to use the Don't Repeat Yourself principle: the code to support *exactly* the same *idea* for local and external tests is similar, but not nearly similar enough to use the same code in both places. So it goes: once again simplicity and consistency is an illusion for the user, gained at considerable cost. Edward P.S. Similarly, all forms of scripting and unit testing now make the source code available to Python's debugger. For local tests, this depends on the @bool write_script_file setting, but the testing harness for external tests doesn't support user options, so when dynamicUnitTest.leo is being executed the variable c.write_script_file is forced to be True. P.P.S. I have added several new unit tests to test the operation of Leo's testing code itself. 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.
