Site Overlay

Tag: ci

CategoriesMozilla

Firefox Automation report – week 33/34 2014

By Admin

In this post you can find an overview about the work happened in the Firefox Automation team during week 33 and 34. Highlights To make sure that our weekly meetings will be more visible to our community, we got them added to the community calendar. If you are interested in what’s going on for Firefox Automation you are welcome to join our Monday’s team meeting. In regards of the Mozmill project, Henrik landed his patch, which makes Mozmill more descriptive in terms of unexpected application shutdowns. Especially in the pastContinue readingFirefox Automation report – week 33/34 2014

CategoriesMozilla

Firefox Automation report – week 31/32 2014

By Admin

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,Continue readingFirefox Automation report – week 31/32 2014

CategoriesMozilla

Firefox Automation report – week 29/30 2014

By Admin

In this post you can find an overview about the work happened in the Firefox Automation team during week 29 and 30. Highlights During week 29 it was time again to merge the mozmill-tests branches to support the upcoming release of Firefox 31.0. All necessary work has been handled on bug 1036881, which also included the creation of the new esr31 branch. Accordingly we also had to update our mozmill-ci system, and got the support landed on production. The RelEng team asked us if we could help in setting upContinue readingFirefox Automation report – week 29/30 2014

CategoriesMozilla

Firefox Automation report – week 27/28 2014

By Admin

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 theContinue readingFirefox Automation report – week 27/28 2014

CategoriesMozilla

Firefox Automation report – week 23/24 2014

By Admin

In this post you can find an overview about the work happened in the Firefox Automation team during week 23 and 24. Highlights To continue the training for Mozilla related test frameworks, we had the 3rd automation training day on June 4th. This time lesser people attended, but we were still able to get a couple of tasks done on oneanddone. Something which bothered us already for a while, is that for our mozmill-tests repository no push_printurl hook was setup. As result the landed changeset URL gets not printed toContinue readingFirefox Automation report – week 23/24 2014

CategoriesMozilla

Firefox Automation report – week 21/22 2014

By Admin

In this post you can find an overview about the work happened in the Firefox Automation team during week 21 and 22. Highlights To assist everyone from our community to learn more about test automation at Mozilla, we targeted 4 full-day automation training days from mid of May to mid of June. The first training day was planned for May 21rd and went well. Lots of [people were present and actively learning more about automation[https://quality.mozilla.org/2014/05/automation-training-day-may-21st-results/). Especially about testing with Mozmill. To support community members to get in touch with MozmillContinue readingFirefox Automation report – week 21/22 2014

CategoriesMozilla

Firefox Automation report – week 19/20 2014

By Admin

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 allContinue readingFirefox Automation report – week 19/20 2014

CategoriesMozilla

Firefox Automation report – week 17/18 2014

By Admin

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 theirContinue readingFirefox Automation report – week 17/18 2014

CategoriesMozilla

Firefox Automation report – week 15/16 2014

By Admin

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 fromContinue readingFirefox Automation report – week 15/16 2014

CategoriesMozilla

Firefox Automation report – week 13/14 2014

By Admin

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 AutomationContinue readingFirefox Automation report – week 13/14 2014

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