IDLE - Test Replace Dialog

[SaimadhavHeblikar]

BPO	21676
Nosy	@terryjreedy
Files	test-replace-34.diff

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = 'https://github.com/terryjreedy'
closed_at = <Date 2016-05-18.00:05:50.997>
created_at = <Date 2014-06-06.06:36:35.223>
labels = ['expert-IDLE', 'type-feature']
title = 'IDLE - Test Replace Dialog'
updated_at = <Date 2016-05-18.00:05:50.994>
user = 'https://bugs.python.org/SaimadhavHeblikar'

bugs.python.org fields:

activity = <Date 2016-05-18.00:05:50.994>
actor = 'terry.reedy'
assignee = 'terry.reedy'
closed = True
closed_date = <Date 2016-05-18.00:05:50.997>
closer = 'terry.reedy'
components = ['IDLE']
creation = <Date 2014-06-06.06:36:35.223>
creator = 'Saimadhav.Heblikar'
dependencies = []
files = ['35493']
hgrepos = []
issue_num = 21676
keywords = ['patch']
message_count = 3.0
messages = ['219863', '265792', '265794']
nosy_count = 4.0
nosy_names = ['terry.reedy', 'jesstess', 'python-dev', 'Saimadhav.Heblikar']
pr_nums = []
priority = 'normal'
resolution = 'fixed'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue21676'
versions = ['Python 3.5', 'Python 3.6']

[SaimadhavHeblikar]

Add unittest for idlelib's replace dialog.
7 lines related to replacedialog logic could not be tested. Any input on how to test those lines?

Running the test suite for idlelib emits:
"ttk::ThemeChanged"
invalid command name "3069198412callit"
while executing
"3069198412callit"
("after" script)
invalid command name "3051229868callit"
while executing
"3051229868callit"
("after" script),

though the tests pass.

If this is fine, will post a 2.7 backport.

[python-dev]

New changeset d8ed90a35505 by Terry Jan Reedy in branch '3.5':
Issue bpo-21676: test IDLE replace dialog. Original patch by Saimadhav Heblikar.
https://hg.python.org/cpython/rev/d8ed90a35505

[terryjreedy]

The 'Theme changed' message is maddening. I verified that is was not occurring without this patch. I made sure all widgets were passed cls.root as master, and that all were delected. Running the class with "def test_dummy(self): pass" and all other methods commented out did not result in the message. So setup and teardown do not, in themselves, cause it. Running the first test, test_simple up to the point where a replace function is caused did not trigger the message. Running most any replace funcition does trigger. The base dialog and search tests do not trigger, so merely creating an engine did not. One new thing in replace test is tests using REs.

Anyway, pushed slightly modified files. I am no longer backporting 'routine' patches to 2.7.