Martin v. Löwis wrote:
> While I'm happy that Barry has automated his part to a high degree,
> my part is, unfortunately, much less automated. I could personally
> automate the build process a bit more, but part of it is also testing
> of the installers, which is manual.
Maybe you could delegate a lot of the testing to competent volunteers?
That's not the issue - I don't mind spending that time. However, it
means that several hours pass between starting the release process, and
making the binaries available - during this time, users always complain
why the Windows binaries are not released yet.
With additional volunteers, availability of the binaries would lag even
more behind the release announcement.
Installer tests can definitely be automated, and there is also a Python
API to the virtualbox VM. I wonder if it would be possible to automate
testing all the installers in various scenarios - each running
simultaneously in a VM.
Michael
[1] Doesn't Windows have a way to send synthetic GUI events to a
program? There ought to be a way to really script that, as the Python
installer process presumbly doesn't change much from release to release.
I also need to involve different machines, e.g. XP machines and Vista
machines, and machines that have Visual Studio installed and machines
that don't. Plus, I need to log into each machine in different ways:
as admin user and non-admin user. The automated GUI testing only really
works for a logged-in user.
Regards,
Martin
_______________________________________________
Python-Dev mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/fuzzyman%40voidspace.org.uk
--
http://www.ironpythoninaction.com/
_______________________________________________
Python-3000 mailing list
Python-3000@python.org
http://mail.python.org/mailman/listinfo/python-3000
Unsubscribe:
http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
