# treeherder Published articles for treeherder. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## running tests by bugzilla component instead of test suite DevFeed: [running tests by bugzilla component instead of test suite]() Original publisher: [Read original article]() Author: elvis314 Published: 2017-12-21T17:07:44Z Content type: article Language: en Sources: [Mozilla Automation]() Topics: [test-coverage](), [Test coverage](), [Tool]() Tags: [code-coverage](), [testdev](), [tests](), [tools](), [treeherder]() ### AI overview The article explores running tests by Bugzilla component instead of test suite or random chunks. It describes potential benefits including component-level code coverage, more deterministic SETA results, component filtering in Treeherder, and easier handling of intermittent tests, while noting that the approach is not production-ready. ### Source excerpt Over the years we have had great dreams of running our tests in many different ways. There was a dream of 'hyperchunking' where we would run everything in hundreds of chunks finishing in just a couple of minutes for all ... Continue reading -> ## Stockwell: flowchart for triage DevFeed: [Stockwell: flowchart for triage]() Original publisher: [Read original article]() Author: elvis314 Published: 2017-10-23T19:50:29Z Content type: article Language: en Sources: [Mozilla Automation]() Topics: [bug](), [Development](), [monitor](), [Tool]() Tags: [bug](), [development](), [intermittent-failures](), [intermittents](), [monitor](), [process](), [testdev](), [treeherder]() ### AI overview This article describes Stockwell's workflow for triaging intermittent failures. Tree sheriffs associate failures with bugs in Treeherder and Orange Factor, after which the Neglected Oranges tool helps identify failures lacking recent human comments. Frequently failing bugs may be monitored and disabled when they exceed the stated failure threshold or lack resources for a fix. ### Source excerpt I gave an update 2 weeks ago on the current state of Stockwell (intermittent failures). I mentioned additional posts were coming and this is a second post in the series. First off the tree sheriffs who maintain merges between branches, ... Continue reading -> ## Firefox for Android Performance Measures - Q3 Check-up DevFeed: [Firefox for Android Performance Measures - Q3 Check-up]() Original publisher: [Read original article]() Author: gbrown-mozilla Published: 2016-09-30T19:57:17Z Content type: article Language: en Sources: [Mozilla Automation]() Topics: [Firefox](), [Android](), [bug](), [SVG]() Tags: [android](), [apk](), [bug](), [firefox](), [firefox-for-android](), [improvements](), [memory](), [mozilla](), [performance](), [performance-measurements](), [startup](), [svg](), [treeherder]() ### AI overview A Q3 performance check-up for Firefox for Android reports improvements in APK size, memory use, and startup time associated with bug 1291424. It also reviews Autophone and Talos measurements, finding no significant improvements or regressions for the reported SVG and page-load tests. ### Source excerpt Highlights: Recent outstanding improvements in APK size, memory use, and startup time, all due to :esawin's efforts in bug 1291424. ... Continue reading -> ## Outreachy Internship Update: Learning Mozilla's Development Process and Refactoring Marionette's Python Test Runner DevFeed: [Outreachy Internship Update: Learning Mozilla's Development Process and Refactoring Marionette's Python Test Runner]() Original publisher: [Read original article]() Author: Anjana Sofia Vakil (contact@anjana.dev) Published: 2016-08-02T00:00:00Z Content type: opinion Language: en Sources: [Mozilla Automation]() Topics: [Development](), [Mozilla](), [Testing](), [Python](), [Refactoring](), [Test-driven development](), [Pytest](), [Firefox]() Tags: [development-process](), [firefox](), [internship](), [marionette](), [mozilla](), [mozreview](), [outreachy](), [pytest](), [python](), [refactoring](), [test](), [testing](), [treeherder]() ### AI overview An Outreachy intern reflects on the first part of an internship with Mozilla, describing the process of learning Mozilla's development tools and workflows. The article also outlines work on test-driven refactoring of Marionette's Python test runner and previews a follow-up post about its test runner and harness. ### Source excerpt It feels like yesterday that I started my Outreachy internship, but it was actually over 2 months ago! For the last couple of weeks I've been on Outreachy hiatus because of EuroPython, moving from Saarbrücken to Berlin, and my mentor being on vacation. Now I'm back, with 6 weeks left in my internship! So it seems like a good moment to check in and reflect on how things have been going so far, and what's in store for the rest of my time as an Outreachyee. What have I been up to? Learning how to do the work In the rather involved application process for Outreachy, I already had to spend quite a bit of time figuring out the process for making even the tiniest contribution to the Mozilla codebase. But obviously one can't learn everything there is to know about a project within a couple of weeks, so a good chunk of my Outreachy time so far was spent on getting better acquainted with: The tools I've already written about my learning experiences with Mercurial, but there were a lot of other components of the Mozilla development process that I had to learn about (and am still learning about), such as Bugzilla, MozReview, Treeherder, Try, Mach... Then, since the project I'm working focuses on testing, I had to grok things like Pytest and Mock. Since most everything I'm doing is in Python, I've also been picking up useful Python tidbits here and there. The project My internship project, "Test-driven refactoring of Marionette's Python test runner", relates to a component of the Marionette project, which encompasses a lot of moving parts. Even figuring out what Marionette is, what components it comprises, how these interrelate, and which of them I need to know about, was a non-trivial task. That's why I'm writing a couple of posts about the project itself - one down, one to go - to crystallize what I've learned and hopefully make it a little easier for other people to get through the what-even-is-it steps that I've been going through. This post is a sort of "intermission", so sta ## Firefox for Android Performance Measures - Q2 Check-up DevFeed: [Firefox for Android Performance Measures - Q2 Check-up]() Original publisher: [Read original article]() Author: gbrown-mozilla Published: 2016-07-04T23:22:49Z Content type: article Language: en Sources: [Mozilla Automation]() Topics: [Firefox](), [Android](), [APK](), [SVG]() Tags: [android](), [apk](), [browser](), [firefox](), [firefox-for-android](), [memory](), [mozilla](), [performance](), [performance-measurements](), [svg](), [treeherder]() ### AI overview A quarterly performance review of Firefox for Android reports gradual increases in APK size and memory use, no significant changes in SVG rendering and generic page-load performance, and newly available Autophone throbber data in Perfherder. ### Source excerpt Highlights: gradual increases in APK size and memory use not much change in tsvgx or tp4m autophone throbber data available ... Continue reading -> ## Firefox-ui-tests - Platform Operations Project of the Month DevFeed: [Firefox-ui-tests - Platform Operations Project of the Month]() Original publisher: [Read original article]() Author: Admin Published: 2016-06-02T09:18:23Z Content type: article Language: en Sources: [Mozilla Automation]() Topics: [Firefox](), [Testing](), [ci](), [Puppeteer](), [Automation](), [Mozilla](), [Jenkins]() Tags: [automation](), [browser](), [ci](), [continuous-integration](), [firefox](), [jenkins](), [marionette](), [mozilla](), [mozmill](), [taskcluster](), [testing](), [tests](), [treeherder]() ### AI overview This article presents firefox-ui-tests as a Mozilla project for integration testing of Firefox's user interface. The tests use the Marionette automation framework and Firefox Puppeteer's page object model, run across Firefox code-check and release workflows, and include localized-build and update testing. The project's work includes improving result visibility, test placement, stability, and coverage. ### Source excerpt Hello from Platforms Operations! Once a month we highlight one of our projects to help the Mozilla community discover a useful tool or an interesting contribution opportunity. This month's project is firefox-ui-tests! What are firefox-ui-tests? Firefox UI tests are a test suite for integration tests which are based on the Marionette automation framework and are majorly used for user interface centric testing of Firefox. The difference to pure Marionette tests is, that Firefox UI tests are interacting with the chrome scope (browser interface) and not content scope (websites) by default.Continue readingFirefox-ui-tests - Platform Operations Project of the Month ## Firefox for Android Performance Measures - Q1 Check-up DevFeed: [Firefox for Android Performance Measures - Q1 Check-up]() Original publisher: [Read original article]() Author: gbrown-mozilla Published: 2016-03-31T15:27:24Z Content type: article Language: en Sources: [Mozilla Automation]() Topics: [Firefox](), [Android](), [APK](), [bug](), [SVG]() Tags: [android](), [apk](), [bug](), [firefox](), [firefox-for-android](), [memory](), [mozilla](), [performance-measurements](), [regression](), [svg](), [treeherder]() ### AI overview A Q1 check-up of Firefox for Android performance measures reports reduced APK size after downloadable fonts were removed, steady memory measurements, and no significant improvements or regressions in the reported SVG and page-load tests. It also describes changes to Autophone testing and the retirement of mozbench. ### Source excerpt Highlights: APK size reduction for downloadable fonts now measuring memory via test_awsy_lite tsvgx and tp4m moved to Autophone APK Size ... Continue reading -> ## First Experiment with TaskCluster DevFeed: [First Experiment with TaskCluster]() Original publisher: [Read original article]() Author: Maja Frydrychowicz Published: 2016-02-09T05:00:00Z Content type: tutorial Language: en Sources: [Mozilla Automation]() Topics: [CI/CD](), [YAML](), [configuration](), [Testing](), [Mozilla](), [Docker](), [Python]() Tags: [build](), [ci](), [configuration](), [continuous-integration](), [docker](), [eslint](), [firefox](), [foss](), [mozilla](), [python](), [taskcluster](), [testing](), [treeherder](), [yaml]() ### AI overview A developer explains how to add and schedule a new task in Mozilla's TaskCluster continuous integration system. The article covers task graphs, YAML configuration, Docker-based execution, source checkouts, and the steps required to register tasks for scheduling and try pushes. ### Source excerpt Adding a new task to TaskCluster continuous integration system. ## Firefox Desktop automation goals Q1 2016 DevFeed: [Firefox Desktop automation goals Q1 2016]() Original publisher: [Read original article]() Author: Admin Published: 2016-02-02T16:39:20Z Content type: article Language: en Sources: [Mozilla Automation]() Topics: [Firefox](), [Automation](), [Testing](), [ci](), [FIRST]() Tags: [automation](), [ci](), [continuous-integration](), [firefox](), [marionette](), [mozilla](), [mozmill](), [qa](), [testing](), [treeherder]() ### AI overview The article outlines Firefox desktop automation goals for Q1 2016, including running firefox-ui-tests in TaskCluster, continuing mozmill-ci coverage within infrastructure limits, reporting results in Treeherder, and documenting the testing systems to support higher-tier sheriffing. ### Source excerpt As promised in my last blog posts I don't want to only blog about the goals from last quarters, but also about planned work and what's currently in progress. So this post will be the first one which will shed some light into my active work. First lets get started with my goals for this quarter. Execute firefox-ui-tests in TaskCluster Now that our tests are located in mozilla-central, mozilla-aurora, and mozilla-beta we want to see them run on a check-in basis including try. Usually you will setup Buildbot jobs toContinue readingFirefox Desktop automation goals Q1 2016 ## Review of automation work - Q4 2015 DevFeed: [Review of automation work - Q4 2015]() Original publisher: [Read original article]() Author: Admin Published: 2016-01-08T22:25:58Z Content type: article Language: en Sources: [Mozilla Automation]() Topics: [Automation](), [Firefox](), [Mozilla](), [Puppeteer](), [GitHub](), [Refactoring](), [bug]() Tags: [automation](), [bug](), [ci](), [code](), [continuous-integration](), [firefox](), [github](), [jenkins](), [marionette](), [misc](), [mozilla](), [mozmill](), [mozqa](), [refactoring](), [script](), [tests](), [treeherder]() ### AI overview A Q4 2015 review of work to move Firefox UI tests into mozilla-central, run them with mozharness in mozmill-ci, fix failures and regressions, split the repository into packages, and improve related test tooling. ### Source excerpt The last quarter of 2015 is gone and its time to reflect what happened in Q4. In the following you will find a full overview again for the whole quarter. It will be the last time that I will do that. From now on I will post in shorter intervals to specific topics instead of covering everything. This was actually a wish from our latest automation survey which I want to implement now. I hope you will like it. So during the last quarter my focus was completely on gettingContinue readingReview of automation work - Q4 2015 ## Engineering Productivity Update, November 5, 2015 DevFeed: [Engineering Productivity Update, November 5, 2015]() Original publisher: [Read original article]() Author: jagriffin Published: 2015-11-05T13:59:20Z Content type: news Language: en Sources: [Mozilla Automation]() Topics: [Mozilla](), [developer tooling](), [Firefox](), [Tool]() Tags: [devtools](), [engineering-productivity](), [mozilla](), [performance](), [taskcluster](), [treeherder](), [version-control](), [windows]() ### AI overview Mozilla's Engineering Productivity team reports progress on Mercurial cloning performance, community contribution, MozReview and Autoland, Treeherder, Perfherder, Android workflows, TaskCluster migration, and e10s testing on Windows. ### Source excerpt It's the first week of November, and because of the December all-hands and the end-of-year holidays, this essentially means the quarter is half over. You can see what the team is up to and how we're tracking against our deliverables with this spreadsheet. Highlights hg.mozilla.org: gps did some interesting work investigating ways to increase cloning [...] ## Firefox Automation report - Q3 2015 DevFeed: [Firefox Automation report - Q3 2015]() Original publisher: [Read original article]() Author: Admin Published: 2015-10-20T19:42:37Z Content type: article Language: en Sources: [Mozilla Automation]() Topics: [Automation](), [Firefox](), [Jenkins](), [Refactoring](), [Puppeteer](), [ci](), [modules]() Tags: [automation](), [blog](), [ci](), [continuous-integration](), [firefox](), [jenkins](), [marionette](), [modules](), [mozilla](), [mozmill](), [refactoring](), [report](), [software](), [taskcluster](), [test](), [treeherder]() ### AI overview A Q3 2015 Firefox Automation report describes work on mozharness scripts for firefox-ui-tests, including improved configurability, crash-report handling, and support for Jenkins and release-testing workflows. It also covers Mozmill-CI updates, test-job refactoring, fixes for update tests affected by Release Engineering changes, and rewritten Pulse-message handling. ### Source excerpt It's time for another Firefox Automation report! It's incredible how fast a quarter passes by without that I have time to write reports more often. Hopefully it will change soon - news will be posted in a follow-up blog post. Ok, so what happened last quarter for our projects. Mozharness One of my deliverables in Q3 was to create mozharness scripts for our various tests in the firefox-ui-tests repository, so that our custom runner scripts can be replaced. This gives us a way more stable system and additional features likeContinue readingFirefox Automation report - Q3 2015 ## Bugzilla Mozilla push includes security, recovery, permissions, and endpoint updates DevFeed: [Bugzilla Mozilla push includes security, recovery, permissions, and endpoint updates]() Original publisher: [Read original article]() Author: glob Published: 2015-09-30T07:42:19Z Content type: release Language: en Sources: [Mozilla Automation]() Topics: [Mozilla](), [Security](), [Process](), [Bot]() Tags: [bmo](), [bots](), [mozilla](), [process](), [recovery](), [release](), [security](), [treeherder](), [update]() ### AI overview A Mozilla Bugzilla push included changes to the whoami endpoint, security notifications, printable recovery 2FA codes, flag timestamps, permissions documentation, and a Treeherder address. ### Source excerpt the following changes have been pushed to bugzilla.mozilla.org: [1207926] change treeherder@bots.tld to orangefactor@bots.tld [1204683] Add whoami endpoint [1208135] security not being mailed when bugs change core-security-release state [1199090] add printable recovery 2fa codes [1204623] timestamp on flags should reference the latest updated activity, not the first [1209745] Update get_permissions.html.tmpl to reflect new self-canconfirm process discuss [...]