This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author terry.reedy
Recipients Todd.Rovito, ezio.melotti, ncoghlan, ned.deily, r.david.murray, terry.reedy
Date 2013-06-15.22:49:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
The basic question for this issue is whether to segregate gui tests in a separate directory (idle_test_gui?) and run them with a separate or to sprinkle gui test cases throughout the test suite, perhaps one to each test_idle/ file?

For development, I am pretty sure I would prefer the latter. I have started test_grep for the 3 methods that can be gui free, but if (when) I do a gui-requiring test of the dialog itself, I would prefer to have it follow in the same file.

However, my impression is that each requires('gui') call will result in a skip message on the test output. (Correct?) So my question is: will non-idle developers tolerate over 50 skip warnings from Idle tests? or is there a way to suppress multiple warnings and consolidate them into just one if there is at least one?
Date User Action Args
2013-06-15 22:49:23terry.reedysetrecipients: + terry.reedy, ncoghlan, ned.deily, ezio.melotti, r.david.murray, Todd.Rovito
2013-06-15 22:49:23terry.reedysetmessageid: <>
2013-06-15 22:49:23terry.reedylinkissue18103 messages
2013-06-15 22:49:23terry.reedycreate