<div dir="ltr">The problem is that what one should test depends highly on what changes have been made. This is true always in the absence of a test suite, I guess. My point is that I can think of quite a few "testing recipes" but their coverage would be rather low, so I'm not sure how useful they would be.<br>
<br>Also, the ability to write tests when fixing bugs which make sure the bugs stay fixed is IMO a basic requirement. Doing this with recipes would make quickly make testing too time consuming.<br><br>Perhaps tests written with something like <a href="http://sikuli.org/">Sikuli</a>?<br>
<br>- Tal<br><br><div class="gmail_quote">On Thu, Apr 14, 2011 at 1:36 AM, Ned Deily <span dir="ltr"><<a href="mailto:nad@acm.org">nad@acm.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
In article <BANLkTimd8hjpTUgusUS=<a href="mailto:1od7en1J8SjJUg@mail.gmail.com">1od7en1J8SjJUg@mail.gmail.com</a>>,<br>
<div class="im"> phil jones <<a href="mailto:interstar@gmail.com">interstar@gmail.com</a>> wrote:<br>
</div><div class="im">> I'd be willing to help with testing of IDLE on Ubuntu if there's a<br>
> need for that. Is there a document (say a wiki page somewhere) which<br>
> tells us what / how to test?<br>
<br>
</div>Not that I'm aware of. Perhaps someone else knows of something? Writing<br>
some test session recipes would be a good start towards repeatable and<br>
possibly more automated testing.<br>
<br>
And thanks all for the testing offers.<br>
<font color="#888888"><br>
--<br>
</font><div class="im"> Ned Deily,<br>
<a href="mailto:nad@acm.org">nad@acm.org</a><br>
<br>
</div><div><div></div><div class="h5">_______________________________________________<br>
IDLE-dev mailing list<br>
<a href="mailto:IDLE-dev@python.org">IDLE-dev@python.org</a><br>
<a href="http://mail.python.org/mailman/listinfo/idle-dev" target="_blank">http://mail.python.org/mailman/listinfo/idle-dev</a><br>
</div></div></blockquote></div><br></div>