Re: #1467: Use traditional unit test (almost?) everywhere

On Sat, 28 Dec 2019 02:17:06 -0800 (PST) "Edward K. Ream" wrote: > Bob's remarks yesterday about unit testing had me look at Leo's unit > testing framework with new eyes. > > #1467 suggest > using traditional unit tests everywhere, or

Leo requires tkinter module to be configured in Python environment

Hello Edward, hello Matt, I just noticed something interesting/ strange/ weird. Actually two issues: First: Leo requires that the tkinter module is configured in the Python installation. (Backgound: I just upgraded to Python 3.7.6 - and - decided to de-select everything but pip ...) Second:

Re: Progress on ViewRendered2

On Fri, Dec 27, 2019 at 6:35 PM Thomas Passin wrote: > I have made a lot of progress on re-implementing *Viewrendered2 *in the > QT5 era, and I wanted to share where I am with it. > Many thanks for this work! Others have expressed interest. > So it's been painful, but progress is good. >

Re: #1467: Use traditional unit test (almost?) everywhere

I've been experimenting lately writing pytest tests for leo. I just published my work at https://github.com/btheado/leo-editor/tree/pytest-experiment. You should be able try it out with these commands (untested): git origin add btheado https://github.com/btheado/leo-editor.git git checkout

Re: #1467: Use traditional unit test (almost?) everywhere

On Saturday, December 28, 2019 at 6:07:03 AM UTC-5, vitalije wrote: For a long time I've been feeling that Leo unit tests don't prove anything. > They usually don't exercise real Leo code at all or if they do, they > exercise just a small portion of it. So, the fact that unit tests are >

Re: Why is Script 'leo-m.exe' not available in Leo 6.1-final on PyPI?

Hello Matt, Am Do., 26. Dez. 2019 um 20:49 Uhr schrieb Matt Wilkie : > Why is the script 'leo-m.exe' available in the development-/ beta version >> of Leo (e.g. 6.1-b1-devel) but not in the master-/ final version of Leo >> (e.g. 6.1-final) at PyPI? >> > > It's because master lags behind devel.

Re: #1467: Use traditional unit test (almost?) everywhere

This is a good idea. I suppose you don't plan to make a lot of changes in the test cases. But even without changing test cases this would be a big step forward. For a long time I've been feeling that Leo unit tests don't prove anything. They usually don't exercise real Leo code at all or if

#1467: Use traditional unit test (almost?) everywhere

Bob's remarks yesterday about unit testing had me look at Leo's unit testing framework with new eyes. #1467 suggest using traditional unit tests everywhere, or maybe almost everywhere. Imo, this will be a significant improvement. I'll

Re: Why is Script 'leo-m.exe' not available in Leo 6.1-final on PyPI?

Hello Thomas, Am Samstag, 28. Dezember 2019 00:54:15 UTC+1 schrieb Thomas Passin: > > > > On Thursday, December 26, 2019 at 2:49:52 PM UTC-5, Matt Wilkie wrote: >> >> Why is the script 'leo-m.exe' available in the development-/ beta version >>> of Leo (e.g. 6.1-b1-devel) but not in the master-/