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
In this post you can find an overview about the work happened in the Firefox Automation team during week 11 and 12. Highlights After Henrik got started on updating the TPS test framework for Firefox Sync tests, he got it into a state that it is working with the new Firefox Accounts feature coming with Firefox 29.0. For details please see bug 966434. Fixing the backward compatibility for the old Sync authentication is his next step. With the release of Mozmill 2.0.6 and the initial support of handling crashes, we
In this post you can find an overview about the work happened in the Firefox Automation team during week 9 and 10. I for myself was a week on vacation. A bit of relaxing before the work on the TPS test framework should get started. Highlights In preparation to run Mozmill tests for Firefox Metro in our Mozmill-CI system, Andreea has started to get support for Metro builds and appropriate tests included. With the help from Henrik we got Mozmill 2.0.6 released. It contains a helpful fix for waitForPageLoad(), which
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.
Given that I was not able to update the design of my website in the last 2 years or so, and my site was kinda broken on phones, tablets, and other smaller devices, I have decided to change the theme. Together with the recent update to WordPress 3.8.2 which came out yesterday, I switched over to the Twenty Forteen theme. It’s based on a responsiveness design and fits perfectly across devices. I know there are pages which might not looks that beautiful yet, but I’m about to update those step
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.
A lot of things were happening in weeks 5 and 6, and we made some good progress regards the stability of Mozmill. Highlights The unexpected and intermittent Jenkins crashes our Mozmill CI system was affected with are totally gone now. Most likely the delayed creation of jobs made that possible, which also gave Jenkins a bit more breath and not bomb it with hundreds of API calls. For the upcoming release of Mozmill 2.0.4 a version bump for package dependencies was necessary for mozdownload. So we released mozdownload 1.11. Sadly
Due to the high work load and a week of vacation I was not able to give some updates for work done by the Firefox Automation team. In the next days I really want to catch up with the reports, and bring you all on the latest state. Highlights After the staging system for Mozmill CI has been setup by IT and Henrik got all the VMs connected, also the remaining Mac Minis for OS X 10.6 to 10.9 have been delivered. That means our staging system is complete and
I promised to keep up with our updates over the last week but given a major breakage in the freshly released version of Mozmill 2.0.4, I had a full week of work to get the fix out. I promise that during this week I will write reports for the weeks in January. Highlights With the new year our team has been reorganized and we are part of the Mozilla QA team again. That means we will have a way closer relationship to any feature owner, and also working towards in