On Thu, Dec 26, 2019 at 6:04 PM SegundoBob <[email protected]> wrote:
> I have never benefited from leo-editor/leo/test/unitTest.leo... Hence, I don't use them. Good to know. Thanks for your detailed report. As noted elsewhere, this entire question is moot. The ability to run unit tests externally will remain. > In my opinion, it is best to use unit tests that impose as few levels of cleverness as possible between the tested program and the test. The unit test directives in Leo-Editor are an unnecessary level of cleverness. I have several responses: 1. Leo's own unit tests might be called a special case. Many unit tests benefit from being able to store outline data in children of @test nodes. 2. I am about to convert the unit tests for leoAst.py into "traditional" unit tests within leoAst.py. This will allow people to use leoAst.py separately from Leo. It will be interesting to compare the two approaches. 3. It's been a long time since the behind-the-scenes machinery involved in running @test nodes has caused any problems for. The convenience in avoiding setup(), teardown() and all the rest is considerable. Binding "self" to the behind-the-scenes instance of unittest.TestCase allows full flexibility when needed. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/CAMF8tS10HOt9V5vhcagfxCqUhPeM2RVDb3OwTSMMXHmZV%3Dci9A%40mail.gmail.com.
