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 ezio.melotti, roger.serwy, terry.reedy
Date 2012-01-16.20:55:41
SpamBayes Score 1.8346413e-09
Marked as misclassified No
Message-id <1326747342.15.0.228834163033.issue13052@psf.upfronthosting.co.za>
In-reply-to
Content
The library manual has chapters for

unittest: the generic testing framework (package) that any app can use

test: a package with the Python test suite; test_x tests module x
  It has other modules and subpackages, probably not all documented.
  The test modules use unittest, doctest, and other code.

test.support: some of the other code

AS it says in the test chapter, the test suite imports each test_x and runs its test_main function. The tkinter package includes a test subpackage. test_tk checks that _tkinter and tk are available and if so, runs the tests in tkinter.test. (But I am not sure it really does what it should ;-).

My thought is that we might want to do something similar with idle. However, there needs to be a test_idle module in any case, so we can start with a few tests there and migrate them to a separate idlelib.test subpackage later if we want.
History
Date User Action Args
2012-01-16 20:55:42terry.reedysetrecipients: + terry.reedy, ezio.melotti, roger.serwy
2012-01-16 20:55:42terry.reedysetmessageid: <1326747342.15.0.228834163033.issue13052@psf.upfronthosting.co.za>
2012-01-16 20:55:41terry.reedylinkissue13052 messages
2012-01-16 20:55:41terry.reedycreate