yaxing.chen
c52c907deb
use local pip
|
5 rokov pred | |
|---|---|---|
| .. | ||
| PaxHeader | 5 rokov pred | |
| test_tkinter | 5 rokov pred | |
| test_ttk | 5 rokov pred | |
| ._README | 5 rokov pred | |
| .___init__.py | 5 rokov pred | |
| ._runtktests.py | 5 rokov pred | |
| ._support.py | 5 rokov pred | |
| ._test_tkinter | 5 rokov pred | |
| ._test_ttk | 5 rokov pred | |
| ._widget_tests.py | 5 rokov pred | |
| README | 5 rokov pred | |
| __init__.py | 5 rokov pred | |
| runtktests.py | 5 rokov pred | |
| support.py | 5 rokov pred | |
| widget_tests.py | 5 rokov pred | |
README
Writing new tests
=================
Precaution
----------
New tests should always use only one Tk window at once, like all the
current tests do. This means that you have to destroy the current window
before creating another one, and clean up after the test. The motivation
behind this is that some tests may depend on having its window focused
while it is running to work properly, and it may be hard to force focus
on your window across platforms (right now only test_traversal at
test_ttk.test_widgets.NotebookTest depends on this).
=================
Precaution
----------
New tests should always use only one Tk window at once, like all the
current tests do. This means that you have to destroy the current window
before creating another one, and clean up after the test. The motivation
behind this is that some tests may depend on having its window focused
while it is running to work properly, and it may be hard to force focus
on your window across platforms (right now only test_traversal at
test_ttk.test_widgets.NotebookTest depends on this).