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 terry.reedy
Date 2016-08-11.04:04:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1470888252.5.0.707581681371.issue27733@psf.upfronthosting.co.za>
In-reply-to
Content
Spinoff of #27732, which changed 5 tested bell-using classes to consistently call 'self.bell()' (instead of self.text.bell or whatever) so tests for such classes could replace the function with a quiet function.  For 4 of the classes, the replacement is currently 'lambda: None'.  For undo, it is a quiet mock that replaced a noisy mock wrapping and calling the original bell().  The purpose of the mock, either way, is to test that bell() is called when intended.

I plan to add a new idle_test.mock_tk.bell function.  I am considering having it automatically reset 'called' when 'called is accessed.  In any case, this issue is about extending the use of mock bells to other tests.
History
Date User Action Args
2016-08-11 04:04:12terry.reedysetrecipients: + terry.reedy
2016-08-11 04:04:12terry.reedysetmessageid: <1470888252.5.0.707581681371.issue27733@psf.upfronthosting.co.za>
2016-08-11 04:04:12terry.reedylinkissue27733 messages
2016-08-11 04:04:12terry.reedycreate