On 5/13/2013 1:28 AM, Jayakrishnan Rajagopalasarma wrote:
There is a need for a proper design in commencing idle unittest
framework, Two suggestions in issue 15392
<http://bugs.python.org/issue15392#> are create test_idle directory
in test sub directory (Lib/test/test_idle) or to create test
directory inside idlelib. (Lib/idlelib/test)
On that discussion these two approaches were proposed as follows,
David Murray said, "best practice would be to have all tests be in
the 'test' sub directory. I moved email/test into test/test_email,
*after developing it*
and I prefer having it there"
email and idle are very different beasts.
Terry J. Reedy said,"I strongly prefer idlelib/test since it will
make developing **much** easier for me on Windows. Also, it would be
part of the optional install of idlelib, as tkinter/test is for
tkinter.Adding test/test_idle will not be too much use until
issue#10652 <http://bugs.python.org/issue10652> is resolved so it
I applied a patch and need to check if it completely resolved the issue.
would actually run with -m test."
It is 2 am Monday for me so I will try to be brief and coherent. I have
a draft of a patch based somewhat on yours. I hope to finish it today
after sleep and upload it. I still prefer idlelib/itest (better than
'test' to avoid masking Lib/test when in idlelib) for multiple reasons
and have a draft explanation of them, which will accompany the patch.
I too would like to do the first commit soon, so I can followup with a
conversion of the calltips tests.
I looked through all the idlelib/*.py modules today and there is not
much else in the way of *automated* tests to convert. There is plenty
for multiple people to do ;-). You help will be appreciated.
Terry
_______________________________________________
IDLE-dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/idle-dev
