Message187545
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. |
|
Date |
User |
Action |
Args |
2013-04-22 02:56:14 | JayKrish | set | recipients:
+ JayKrish, terry.reedy, ncoghlan, ned.deily, ezio.melotti, roger.serwy, r.david.murray, Todd.Rovito, tshepang, francismb, Tomoki.Imai |
2013-04-22 02:56:14 | JayKrish | set | messageid: <1366599374.38.0.619005020547.issue15392@psf.upfronthosting.co.za> |
2013-04-22 02:56:14 | JayKrish | link | issue15392 messages |
2013-04-22 02:56:14 | JayKrish | create | |
|