Jayakrishnan added the comment: There is a need of a proper design in whether to put tests in test sub directory or to create idlelib/test directory.
For my GSoc proposal initial draft, I suggested to start with Put tests in test/test_idle directory (like test/test_email would be the best practice). Test for the presence of idle and skip if idle is not available. Move the existing,pending tests for idle ( http://bugs.python.org/file27613/issue16226_test.patch , http://bugs.python.org/file24075/test_idlelib.py,....) into this directory. (which my patch 15392_idletestframework_1.patch did for me) Considering the point terry.reedy mentioned, "Adding test/test_idle will not be too much use until issue #10652 is resolved so it would actually run with -m test", my view is, the issue #10652 on this message is on a healthy patch review, so it would actually run with -m test in near-future Expecting your suggestions on this design decisions. ---------- keywords: +patch Added file: http://bugs.python.org/file29973/15392_idletestframework_1.patch _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue15392> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
