On Sunday, October 14, 2018 at 5:52:08 AM UTC-5, Edward K. Ream wrote: #994 <https://github.com/leo-editor/leo-editor/issues/994> suggests running > pytest from unitTest.leo. >
Rev 3dab6d161 is a good start. It defines `@test run pytests` in unitTest.py. This script runs a new file, leo-editor/run_pytest_tests.py for each directory in a list. Each invocation of run_pytest_tests.py runs in a separate process. The @test test succeeds if and only if no run_pytest_tests.py does writes (directly or indirectly) to stderr. For debugging, the @test node also echos stdout. This is useful, because it indicates which directories contain no pytest tests. At present, no tests are run in the leo/test directory because some test creates two top-level files named a and b. That's not good. I'll investigate. *To do* We should decide (and test) where tests belong. I would prefer as close as possible to the code under test. In the same node (or a child node) would be the best style, imo. Terry's switcheroo button is only a workaround. 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
