Terry J. Reedy <tjre...@udel.edu> added the comment:
I (we) agree that idlelib needs even better test coverage. Some history: 1. I added idle_test/ 5-1/2 years ago. Only the calltip module had automated tests easily converted to unittests (test_calltip). 2. Other exiting tests, requiring human judgement, were debugged, completed, and converted to 'htests', driven by idle_test.htest. Properly measuring idlelib coverage requires excluding htest code (up to 20% of a module). 3. idle_test/README.txt has information on testing IDLE and local conventions. Perhaps more should be added about mocking. 4. We should now be using ttk widgets whenever possible. I would like to add an up-to-date widget-testing doc. Some modules need doctests and a bit of refactoring before adding tests. Tests for a specific module should be a separate issue. Testing tkinter is hard. Can you tell us a bit about your python, tkinter, and testing experience? Cheryl Sabella wrote the majority of tests added in the last year+, and Tal Einat wrote test_squeezer. I suggest you review some of their recent work. They should be able to answer most questions as well as me. ---------- nosy: +cheryl.sabella, taleinat title: low test coverage for idlelib -> Improve test coverage for idlelib versions: +Python 3.7, Python 3.8 _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue35668> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
