The new version of Mozmill brings some under the hood changes to the Python back-end.
The patch on Bug 533227 adds report support for restart tests which can push results to a couchdb instance now. With Mozmill 1.3 only normal Mozmill tests had that capability.
Further we have improved the handling of Python callbacks from within Mozmill tests. While the former version of Mozmill has only supported those callbacks for restart tests, you can use them in normal tests (Bug 538058) now. The only restriction is that the test-run has to be started from the command line client. Users with only the extension installed will not have access to this feature. In the future we will probably use it to implement handling of system level elements and events. Ongoing work can be checked on Bug 525060.
Another great enhancement we are proud to announce are the simplified steps to install Mozmill as command line client on Windows. The only requirement we have is the Mozilla Build environment. There is no need to install Python or the pywin32 extension in parallel anymore. Complete instructions can be found on MDC. A big thanks goes to Atul Varma for his contribution. You helped us a lot!
For more information check-out the complete list of fixes.
Mozmill 1.4 is still in the review queue on addons.mozilla.org. It will take a bit until it is officially available there. So for now grab a copy from Mikeal’s repository and give it a try.
1. The link to AMO is /de/, please link to /en-US/.
2. There’s still one dependency on pywin32, as harthur points out in the bug.
Thanks for the notice. I have updated the link on AMO. For bullet point 2 I feel that it will not affect as many users. Probably it only happens when using Mozrunner instead of Mozmill. It should be handled as a separate bug and fixed for the next release.
Well, the commandline version of Mozmill uses Mozrunner to run Fx/Tb, right? AFAIK that’s the version of Mozmill which had the pywin32 dependency in the first place.
python callbacks and restart test reporting, Woohoo! Nice work to all those involved. BTW, typo in your last paragraph referencing addons.mozilla.org.
Sid, this is really strange. We will track that issue in Bug 542000