EngineeringProductivity
The Engineering Productivity Team
Welcome to the home page of the Platform group's Engineering Productivity team. Formerly known as the Automation and Tools team, we still sometimes use the nickname "A-Team", and you'll see A-Team references scattered around our documentation.
We're a group of engineers who develop and support a wide range of services, tools and automation that serve the engineering teams at Mozilla, with a specific focus on work that increases the productivity of those teams.
Our Mission
The Engineering Productivity Team is a Swiss Army Knife of engineers dedicated to improving the quality and productivity of engineering at Mozilla. Working with others in a responsive and agile manner, we strive to be a model of open development. We create, maintain, and extend a diverse array of sustainable tools and systems that create and deliver information on the quality of Mozilla's products and enhance the impact and effectiveness of the Mozilla community.
Connecting with the Team
We're a friendly bunch of people who are happy to help you; we want to hear about your ideas and your problems and what you think we could do to make your work more productive.
See our Team Roster for a list of people on the team; find us on IRC on #ateam; e-mail us at auto-tools__at__mozilla_dot_com (internal list) or mozilla-tools__at__lists_dot_mozilla.org (external mailing list).
What We Work On
We work on a range of things which varies from quarter to quarter, but the lists below represent the general scope of our activities.
- Services: Bugzilla, MozReview, Autoland, Treeherder/Perfherder, OrangeFactor, hg.mozilla.org, git.mozilla.org, Pulse, ActiveData, Bugzilla ES, TestInformant, sheriffing of the tree
- Automation: Marionette, mochitest, xpcshell, reftest, web-platform-tests, Talos, MozBench, Robocop, Autophone, Bughunter, media and update tests for Firefox, GoFaster, CI integration (buildbot/TaskCluster), W3C WebDriver Specification, new test harnesses as needed
- Tools: mach, mozbase, mozregression, mozdownload, mozharness, mozci, SETA, code coverage
What We Don't Work On
We don't own buildbot or TaskCluster (those belong to the Release Engineering and TaskCluster teams, respectively), although we help on those projects from time to time.
We don't write unit tests which are run in the test harnesses we own; developers are best-suited and responsible for that.
We generally don't write functional tests which are run in the harnesses we own, although we may help out here from time to time, particularly when this is done in conjunction with developing a new harness. Our interests here are empowering developers to write their own tests, but we sometimes contribute tests here as part of the bootstrapping process. Ultimately, as with unit tests, developers are best-suited to writing functional tests and understanding overall test coverage and design.