[Idle-dev] Talking of updates to IDLE
taleinat at gmail.com
Fri Apr 15 01:32:13 CEST 2011
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/>?
On Thu, Apr 14, 2011 at 1:36 AM, Ned Deily <nad at acm.org> wrote:
> In article <BANLkTimd8hjpTUgusUS=1od7en1J8SjJUg at mail.gmail.com>,
> phil jones <interstar at 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,
> nad at acm.org
> IDLE-dev mailing list
> IDLE-dev at python.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the IDLE-dev