Today we hold our last Automation Training day for this quarter. So if you want to learn something about test automation at Mozilla, feel free to join at any time during the day. We are around all day, waiting to answer your questions, and to get you started if you want to contribute to one of our projects. Please have a look at our etherpad for the current status: https://etherpad.mozilla.org/automation-training I’m looking forward to see some of you!
In this post you can find an overview about the work happened in the Firefox Automation team during week 17 and 18. Highlights In one of the last automation reports I mentioned that we wanted to finish up the already in-progress Mozmill tests for Firefox Metro. With lots of work mostly done by Daniel we were finally able to close all the bugs as fixed. Now everyone is back on top of our new quarterly goals. To allow new contributors of the mozmill-tests repository to pick appropriate reviewers for their
The Firefox QA Automation team is hosting another Automation Training day on June, 4th. The event is a day long, so join us whenever you are free. You will be able to learn details about our projects, how we tackle automation requests, or simply to get started with coding. We are always around to assist you in getting started. We are looking out for you and your participation.
In this post you can find an overview about the work happened in the Firefox Automation team during week 15 and 16. Highlights To be able to support the new update path for Firefox Beta users via a final release candidate on the beta channel, we had to update our update testruns with Mozmill in the mozmill-automation repository. Further we also had to add support for this update path in Mozmill CI. Cosmin spend his time on those patches, and finally we got those out and active. That means from