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.
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. Perhaps tests written with something like Sikuli <http://sikuli.org/>? - Tal On Thu, Apr 14, 2011 at 1:36 AM, Ned Deily <n...@acm.org> wrote: > In article <BANLkTimd8hjpTUgusUS=1od7en1j8sj...@mail.gmail.com>, > phil jones <inters...@gmail.com> wrote: > > I'd be willing to help with testing of IDLE on Ubuntu if there's a > > need for that. Is there a document (say a wiki page somewhere) which > > tells us what / how to test? > > Not that I'm aware of. Perhaps someone else knows of something? Writing > some test session recipes would be a good start towards repeatable and > possibly more automated testing. > > And thanks all for the testing offers. > > -- > Ned Deily, > n...@acm.org > > _______________________________________________ > IDLE-dev mailing list > IDLE-dev@python.org > http://mail.python.org/mailman/listinfo/idle-dev >
_______________________________________________ IDLE-dev mailing list IDLE-dev@python.org http://mail.python.org/mailman/listinfo/idle-dev
