Site Overlay

Tag: mozmill

CategoriesMozilla

Automation Development report – week 51/52 2013

By Admin

Wow, somehow I totally missed to send out reports for our automation work. Most likely that happened because of the amount of work I had in the past couple of weeks. So for now lets do a final update before the title will be updated to ‘Firefox Automation report’ by the year 2014. Highlights We have released Mozmill 2.0.3 to fix a couple of issues (see dependencies on bug 950831 seen with Firefox Metro builds and our Firefox shutdown code. We pushed those changes together with the releases of mozmill-automationContinue readingAutomation Development report – week 51/52 2013

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

Mozmill speed improvements after upgrading Python from 2.6 to 2.7.3

By Admin

Yesterday we tried to upgrade our mozmill-ci cluster to the previously released Mozmill 2.0.1. Sadly we failed on the OS X 10.6 machines and had to revert this change. After some investigation I found out that incompatibility issues between Python 2.6 and 2.7.3 were causing this problem in mozprofile. Given the unclear status of Python 2.6 support in mozbase, and a talk in the #ateam IRC channel, I have been advised to upgrade those machines to Python 2.7. I did so after some testing, also because all other machines areContinue readingMozmill speed improvements after upgrading Python from 2.6 to 2.7.3

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

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

CategoriesMozilla

Automation Development report – week 42 2013

By Admin

Highlights Henrik finally updated the current quarterly goals for our team. Please see our prioritized projects or check his blog post from today. We were surprised to see a bug for the httpd.js component fixed after more than a year, which drastically improved the execution time of our Mozmill tests. Given that we are still not able to upgrade our CI system to Mozmill 2.0, another release off the 1.5 branch had to go out. So we made Mozmill 1.5.24 available for everyone. With the help of IT, Henrik wasContinue readingAutomation Development report – week 42 2013

CategoriesMozilla

Automation Development team goals for Q4 2013

By Admin

I know that I’m a bit late in publishing our Automation Development team goals for the last quarter this year. But better late than never. I think there are some very interesting tasks we want to tackle on over the course of the next three months. And we would invite everyone who has interest to join us, learn new stuff, and simply have fun with coding. Given that we are a part of the https://wiki.mozilla.org/Auto-tools team aka the A-Team, we inherit some of the overall team goals for Q4 2013.Continue readingAutomation Development team goals for Q4 2013

CategoriesMozilla

Automation Development report – week 41 2013

By Admin

Similar to last week a couple members from our team were partly away last week given the return travels from the Mozilla Summit. So we have lesser announcements to make, except that we hopefully found a couple of new volunteers for test automation! Which would be fantastic. Highlights As of last week we got our new Mac Minis in SCL3 setup by IT. That means that we have expanded our Mozmill-CI to also run pulse triggered tests for all supported versions of Firefox on OS X 10.9. Since then 2Continue readingAutomation Development report – week 41 2013

CategoriesMozilla

Mozmill 1.5.24 released

By Admin

As of yesterday we have released Mozmill 1.5.24. That release was a bit unexpected because we had already decided to not release another version of this branch. But we were able to include a bug fix, which let our tests run nearly twice that fast. And given that we cannot upgrade our Mozmill CI to version 2.0 yet, a quick 1.5 release provides us a huge performance win. The problem in detail was in the local HTTP server we make use of, which is httpd.js. In July 2012 I recognizedContinue readingMozmill 1.5.24 released

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