cpython/Lib/test/test_tkinter
Serhiy Storchaka 21ed1e2a94
gh-65784: Add support for parametrized resource wantobjects in regrtests (GH-143570)
This allows to run Tkinter tests with the specified value of
tkinter.wantobjects, for example "-u wantobjects=0".
2026-01-16 18:38:38 +02:00
..
__init__.py gh-65784: Add support for parametrized resource wantobjects in regrtests (GH-143570) 2026-01-16 18:38:38 +02:00
__main__.py
README
support.py gh-65784: Add support for parametrized resource wantobjects in regrtests (GH-143570) 2026-01-16 18:38:38 +02:00
test_colorchooser.py gh-65784: Add support for parametrized resource wantobjects in regrtests (GH-143570) 2026-01-16 18:38:38 +02:00
test_font.py gh-65784: Add support for parametrized resource wantobjects in regrtests (GH-143570) 2026-01-16 18:38:38 +02:00
test_geometry_managers.py gh-65784: Add support for parametrized resource wantobjects in regrtests (GH-143570) 2026-01-16 18:38:38 +02:00
test_images.py gh-65784: Add support for parametrized resource wantobjects in regrtests (GH-143570) 2026-01-16 18:38:38 +02:00
test_loadtk.py gh-65784: Add support for parametrized resource wantobjects in regrtests (GH-143570) 2026-01-16 18:38:38 +02:00
test_messagebox.py gh-65784: Add support for parametrized resource wantobjects in regrtests (GH-143570) 2026-01-16 18:38:38 +02:00
test_misc.py gh-65784: Add support for parametrized resource wantobjects in regrtests (GH-143570) 2026-01-16 18:38:38 +02:00
test_simpledialog.py gh-65784: Add support for parametrized resource wantobjects in regrtests (GH-143570) 2026-01-16 18:38:38 +02:00
test_text.py gh-65784: Add support for parametrized resource wantobjects in regrtests (GH-143570) 2026-01-16 18:38:38 +02:00
test_variables.py gh-65784: Add support for parametrized resource wantobjects in regrtests (GH-143570) 2026-01-16 18:38:38 +02:00
test_widgets.py gh-65784: Add support for parametrized resource wantobjects in regrtests (GH-143570) 2026-01-16 18:38:38 +02:00
widget_tests.py gh-124111: test macOS CI with Tk 9 (#137424) 2025-10-14 00:00:58 -04:00

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).