In this post you can find an overview about the work happened in the Firefox Automation team during week 35 and 36. Highlights Due to a lot of Mozmill test failures related to add-on installation and search, we moved from the addons-dev.allizom.org website to the staging website located at addons.allizom.org. Since then we experiencing way lesser test failures, which are most likely network related. In order to keep up with all test failures, and requests for new tests we started our Bug triage meeting on a weekly basis on Friday.
In this post you can find an overview about the work happened in the Firefox Automation team during week 31 and 32. It’s a bit lesser than usual, mainly because many of us were on vacation. Highlights The biggest improvement as came in during week 32 were the fixes for the TPS tests. Cosmin spent a bit of time on investigating the remaining underlying issues, and got them fixed. Since then we have a constant green testrun, which is fantastic. While development for the new TPS continuous integration system continued,
In this post you can find an overview about the work happened in the Firefox Automation team during week 27 and 28. Highlights Henrik continued his work on our QA specific PuppetAgain setup. One of the blockers for us was bug 997721, which is the full proxy support on OS X and Linux. By week 27 we were finally able to get this finished. Further Henrik also got the manifest for installing Java done. On TPS we also made progress. So Cosmin got the Pulse listener script implemented for the
In this post you can find an overview about the work happened in the Firefox Automation team during week 19 and 20. Highlights When we noticed that our Mozmill-CI production instance is quickly filling up the /data partition, and having nearly no space left to actually run Jenkins, Henrik did a quick check, and has seen that the problem were the update jobs. Instead of producing log files with about 7MB in size, files with more than 100MB each were present. Inspecting those files revealed that the problem were all
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
In this post you can find an overview about the work happened in the Firefox Automation team during week 13 and 14. Highlights Finally we were able to upgrade our mozmill-ci production system to Mozmill 2.0.6. The only caveat is that we had to disable one test for cleaning history to prevent the always occurring Flash crash on Windows. This week Henrik was able to land the first fixes for broken TPS tests. Together with Andrei we were able to fix 4 of them. Also we had our first Automation
The current work load is still affecting my time for getting out our automation status reports. The current updates are a bit old but still worth to mention. So lets get them out. Highlights As mentioned in my last report, we had issues with Mozmill on Windows while running our restart tests. So during a restart of Firefox, Mozmill wasn’t waiting long enough to detect that the old process is gone, so a new instance has been started immediately. Sadly that process failed with the profile already in use error.
Building software is fun. Spending countless hours or even days on something to get it finally working. Helping someone who uses your software to speed-up the daily workflow. All that is fantastic and every developer loves that. But don’t let the dark side come up, when customers are pointing you to a lot of software defects. Are you still proud and will you continue the work as how you did it before? Most likely not. Or well, lets say at least not when quality is what you want to ship.