All the details about this all day event you can read here.
Please spread the news around so that we will have a fruitful day with a lot of discussions, and small or larger tasks accomplished.
In this post you can find an overview about the work happened in the Firefox Automation team during week 13 and 14.
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 Training days. The first one on Monday was a huge success, and we have seen lots of new faces. Sadly the second one on the following Wednesday we haven’t announced separately, so lesser people joined our training. In the future we will make sure, to announce each Automation Training day separately. Also there will be only a single one in a full week, so it will allow people to do some homework until the next session.
In week 14 we released version 220.127.116.11 of our mozmill-automation package. It was necessary to allow QA to run the Mozmill update tests with overriding the update channel, so update tests from a release candidate to the next beta build can be performed.
After we discovered even more Flash crashes of the same type, we decided to use the debug version of Flash on our Windows systems. Main reason is that those builds don’t crash. Sadly, given that they would give us way more information. But Adobe should at least know where the crash is happening. Also given that we do not have any private data on our test machines, we decided to actually upload a minidump from one of those crashes to Bugzilla. This information actually helped Adobe a lot! So we will continue doing that.
Last but not least Henrik was able to fix another 7 bugs for TPS. Those were broken tests, a broken behavior of the TPS test extension, or enhancements.
For more granular updates of each individual team member please visit our weekly team etherpad for week 13 and week 14.
If you are interested in further details and discussions you might also want to have a look at the meeting agenda, the video recording, and notes from the Firefox Automation meetings of week 13 and week 14.
In this post you can find an overview about the work happened in the Firefox Automation team during week 11 and 12.
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 found a major Adobe Flash crash on our Windows nodes when clearing cookies. We started to investigate and reported the problem appropriately, so that Adobe is aware of it.
For other crashes which are related to Firefox directly we would still have to retrieve and print the stack to the console. But we cannot do this until the crashreporter symbols are available for Nightly builds on ftp.mozilla.org. We will continue implementing this feature into Mozmill once the former bug has been fixed.
Given that the release of Firefox 28 was upcoming, Andreea has taken care of all the mozmill-tests related branch merges.
To be prepared for our first Automation Training days, Cosmin updated our Mozmill Crowd extension to ease the first steps for new contributors to our projects. Now the extension is working again for all the latest Firefox releases.
Even with the Firefox Metro projects seeing canceled, we want to finalize our nearly ready Mozmill tests for Firefox Metro and get them landed. That way we can pick up development, if necessary in the future. So Daniel was able to get additional 4 tests finished by this week.
In week 12 Henrik finished the basic implementation work for TPS in being able to switch between Firefox Accounts and the old Sync authentication. Both methods are working now and can be used for testing. As next step we have to investigate and fix all the remaining failing TPS tests.
For more granular updates of each individual team member please visit our weekly team etherpad for week 11 and week 12.
If you are interested in further details and discussions you might also want to have a look at the meeting agenda, the video recording, and notes from the Firefox Automation meetings of week 11 and week 12.