Name |
Date |
Size |
#Lines |
LOC |
||
|---|---|---|---|---|---|---|
| .. | - | - | ||||
| test_tkinter/ | 03-May-2024 | - | 3,000 | 2,541 | ||
| test_ttk/ | 03-May-2024 | - | 2,563 | 1,835 | ||
| README | D | 03-May-2024 | 566 | 15 | 11 | |
| __init__.py | D | 03-May-2024 | 0 | 1 | 0 | |
| runtktests.py | D | 03-May-2024 | 2.2 KiB | 70 | 56 | |
| support.py | D | 03-May-2024 | 3.3 KiB | 106 | 88 | |
| widget_tests.py | D | 03-May-2024 | 19.6 KiB | 549 | 446 |
README
1Writing new tests 2================= 3 4Precaution 5---------- 6 7 New tests should always use only one Tk window at once, like all the 8 current tests do. This means that you have to destroy the current window 9 before creating another one, and clean up after the test. The motivation 10 behind this is that some tests may depend on having its window focused 11 while it is running to work properly, and it may be hard to force focus 12 on your window across platforms (right now only test_traversal at 13 test_ttk.test_widgets.NotebookTest depends on this). 14 15