From MozillaWiki
Jump to: navigation, search

Welcome to the Automation and Tools Projects Page.

We are the people who write the code that enables all our automated test systems (correctness, performance etc) to run. We are continually expanding, upgrading, and inventing new and better ways to do automated quality analysis at Mozilla. Most of our systems run on a per-checkin basis, and at the time of this writing we do roughly 300 checkins a day, and we run hundreds of thousands of tests per checkin, so you can imagine how many times our code gets run. If you like the idea of that kind of a challenge, we could use your help on some of the projects below. If you don't know how to get started, feel free to hop on irc (, into the channel #ateam and ask some questions.

The Goals

See our goals page.

Other Projects

Every quarter there are more things we'd like to do than we have time for. Below are some of these projects, broken down by areas and technologies so that you can find something that gets you excited.


Work in progress effort to create an index for all existing/WIP automation tools - Here.

Firefox for Android

The Firefox for Android project is a continual expansion of our test harnesses to better support the Android platform. Currently we only release Firefox on that platform (aka Fennec), but we might also begin testing web apps there in the near future. Familiarity with Android and a great knowledge of Python is very useful here.

  • Help expand our reach to x86 Android systems by aiding us in debugging and fixing test failures on that platform: see the collection of bugs beneath bug 891959

Firefox Desktop and General Automation Support

The desktop web browser Firefox continues to be our flagship product, and there is always ongoing work needed to ensure that we continue to support the new features that regularly land in Firefox. Many of the bugs here are more tractable simply because the test harnesses and tests involved are older code. This is a good spot for first-time contributors. These will involve Python knowledge and some JavaScript, depending on the bug.


The a-team maintains many of the systems and code that perform per-checkin testing on performance. There are many performance automation systems at Mozilla, and one of our current efforts is to pull them under one high-level dashboard, called Perfherder. A working knowledge of the web, Python, JavaScript, statistics, and great debugging skills would be helpful.

Tools & Dashboards

We create web-based tools and dashboards to help illustrate how our automation is doing. Datazilla is a performance dashboarding system, and Treeherder surfaces the status of our automation runs. We also maintain and continually improve Mozilla's Bugzilla installation, often contributing patches to the upstream general Bugzilla project. Python, JavaScript, and, in Bugzilla's case, Perl, are all used here, along with both relational and NoSQL databases.

ATeam Handbook

The ATeam Handbook is meant to be the definitive source of information on how we do things in the ateam, useful for new and old contributors alike. Currently in the planning phase.

Mentored Bugs

These bugs are things that we have identified as great starter bugs. Each bug contains a focused technology that is required and a mentor who has volunteered to help out people starting to work on the issue. If you've done a few mentored bugs, talk to your mentors about becoming a mentor yourself!

Full Query
ID Summary Priority Status Bug mentor
682901 catch the case where .finish() gets called before waitForExplicitFinish() -- NEW No bug_mentor
847275 make assertions cause test failures in mochitest-browser-chrome -- NEW No bug_mentor
939755 With httpd.js we sometimes don't get the most recent version of the file -- NEW No bug_mentor
958147 Choose one of run-if or skip-if and get rid of the other -- NEW No bug_mentor
969334 mozinstall should not magically try to find the mount point of the DMG -- NEW No bug_mentor
1028895 Mouseover triggered in mochitest-browser & dt according to position of mouse cursor on test box -- NEW No bug_mentor
1036328 Support bisection in case of timeout/crash -- NEW No bug_mentor
1072912 Remove makefile targets for running tests from -- NEW No bug_mentor
1137691 SpecialPowers.getFocusedElementForWindow is misnamed -- NEW No bug_mentor
1164443 Mozinstall should only install in an empty dir P3 NEW No bug_mentor
1177336 mozfile.remove uses excessive system calls -- NEW No bug_mentor
1191446 Create a mach command for rerunning failed jobs on a previous push using new code -- NEW No bug_mentor
1192866 Throw an exception when a non-top-level window is passed to synthesizeKey -- NEW No bug_mentor
1199700 add feature to make collecting nspr logs easier in reftest -- NEW No bug_mentor
1255815 [mozinfo] Move |update_mozinfo| from mochitest to mozinfo -- NEW No bug_mentor
1311429 Reftest harness should use mozcrash.kill_and_get_minidump -- NEW No bug_mentor
1337013 Make gtest mach command invoke -- NEW No bug_mentor
1367544 crashtest crash in e10s just hangs the crashtest harness P3 NEW No bug_mentor
1374456 if last reftest in test run crashes, harness restarts and reports 'REFTEST ERROR | EXCEPTION: No tests to run' -- NEW No bug_mentor
1378174 [mozlog] Create a "sugar" formatter based on pytest-sugar P3 NEW No bug_mentor
1403677 [meta] Implement support for cropping of screenshots -- NEW No bug_mentor
1408754 Add configuration to send page to about:tabcrashed -- NEW No bug_mentor
1420372 Marionette client has to check for a valid pid of Firefox as returned with the capabilities P3 NEW No bug_mentor
1443922 Use toolkit.asyncshutdown.crash_timout as shutdown monitor base value P3 NEW No bug_mentor
1446965 [mozlog] Buffer all test logs in 'mach' formatter and flush on failure P3 NEW No bug_mentor
1501669 Simplify command building logic P3 NEW No bug_mentor
1528192 Add an option to use local page recordings instead of tooltool P3 NEW No bug_mentor
1584940 Make measurement units in perf tests mandatory P3 NEW No bug_mentor
1585677 [mozproxy] Use mozbuild's tooltool in mozproxy P2 NEW No bug_mentor
1592764 Error from missing Intel Power Gadget app trips up mozrunner, overwriting its original error P3 NEW No bug_mentor
1633890 [perfdocs] Make the raptor test descriptions less redundant P3 NEW No bug_mentor
1645488 Make it possible to provide a custom Firefox binary to Talos in mach talos P3 NEW No bug_mentor
1682239 Use anyhow crate for handling errors in geckodriver P3 NEW No bug_mentor
1732181 Removed unused chromedriver versions from browsertime fetch task P3 NEW No bug_mentor
1741715 Migrate "SpecialPowers" MDN doc to Firefox Source Docs P3 NEW No bug_mentor
1774850 Missing XPCshell Test Manifest Expressions doc -- UNCONFIRMED No bug_mentor
1815453 [meta] Put all mochitest test manifest files under toolkit/ into alphabetical order. -- NEW No bug_mentor
1823371 Use a document-builder approach instead of data URLs for `inline()` usage in unit tests P3 NEW No bug_mentor
1826828 Add ability to run custom browsertime tests on browsers other than firefox P3 NEW No bug_mentor
1847875 Missing "id" in "Switch To Frame" command does not raise "invalid argument" error P3 NEW No bug_mentor
1866273 Use thiserror crate for webdriver -- ASSIGNED No bug_mentor

41 Total; 41 Open (100%); 0 Resolved (0%); 0 Verified (0%);

For reference, the old Projects Page (which is largely out of date, but interesting for historical reasons) is accessible here