Site Overlay

Tag: firefox

CategoriesMozilla

Firefox Automation report – week 11/12 2014

By Admin

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, weContinue readingFirefox Automation report – week 11/12 2014

CategoriesMozilla

Firefox Automation report – week 9/10 2014

By Admin

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(), whichContinue readingFirefox Automation report – week 9/10 2014

CategoriesMozilla

Firefox Automation report – week 5/6 2014

By Admin

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. SadlyContinue readingFirefox Automation report – week 5/6 2014

CategoriesMozilla

Firefox Automation report – week 3/4 2014

By Admin

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 andContinue readingFirefox Automation report – week 3/4 2014

CategoriesMozilla

Firefox Automation report – week 1/2 2014

By Admin

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 inContinue readingFirefox Automation report – week 1/2 2014

CategoriesMozilla

Automation Development report – week 49/50 2013

By Admin

It’s getting closer to Christmas. So here the 2nd last automation development report for 2013. Also please note that all team members including myself, who were dedicated to Firefox Desktop automation, have been transitioned back from the A-Team into the Mozilla QA team. This will enable us to have a better relationship with QA feature owners, and get them trained for writing automated tests for Firefox. Therefor my posts will be named “Firefox Automation” in the future. Highlights With the latest release of Firefox 26.0 a couple of merges inContinue readingAutomation Development report – week 49/50 2013

CategoriesMozilla

Automation Development report – week 47/48 2013

By Admin

This is again an overview about the highlights of our work in week 47 and 48 this year. Sorry for the delay of a couple of days but some critical work was holding me off from writing this post. Highlights Henrik and Dave were working on a couple of Mozmill-CI updates, which have been pushed to production. The first batch of features and bug fixes landed in week 47. It included the monitoring plugin for Jenkins, which hopefully will help us to figure out the reasons of Java crashes. AlsoContinue readingAutomation Development report – week 47/48 2013

CategoriesMozilla

Automation Development report – week 45/46 2013

By Admin

After the last report over a two week cycle, I have to follow-up with another one for the weeks 45 and 46. Due to my move I had limited availability and to fix some important other stuff. So hopefully this is the last report over a two weeks period in the near future. Highlights To be able to release Mozmill 2.0.1 as soon as possible Henrik had to fix a lot of existent bugs for mozprofile in conjunction with its add-on manager class. Those fixes were necessary because our restartContinue readingAutomation Development report – week 45/46 2013

CategoriesMozilla Software

Mozdownload 1.10 released

By Admin

As of now we have released a new version of mozdownload. The 1.10 release contains a couple of new features, bug fixes, and absolutely to mention a suite of tests. A big thank you goes here to Johannes and Jarek. Both spend a lot of time again, to make it a successful and lesser bug prone release. Here some major items to highlight: Addition of tests for all types of scrapers and a lot for command line options Output of all candidate builds founds if build number has been specifiedContinue readingMozdownload 1.10 released

CategoriesMozilla

Automation Development report – week 43/44 2013

By Admin

Given that I was partly away in the last two weeks I haven’t had the time to write another summary report of our work yet. So lets combine the last two weeks in a single blog post this time. Highlights To be able to continue our work to speed-up testruns in Mozmill CI Henrik upgraded our Mozmill-CI system to Jenkins 1.509.4. This step was necessary so that we can investigate the slowness in sending out emails for finished testruns, which could take up to 25 minutes! Beside that Henrik alsoContinue readingAutomation Development report – week 43/44 2013

By continuing to use the site, you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.

Close