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!

ID Summary Priority Status Bug mentor
592653 Use Services.prefs instead of preferences-service / gPrefService -- ASSIGNED
682901 catch the case where .finish() gets called before waitForExplicitFinish() -- NEW
847275 make assertions cause test failures in mochitest-browser-chrome -- ASSIGNED
884828 mozinstall.get_binary() should check for executable bit and be less confusing -- ASSIGNED
939755 With httpd.js we sometimes don't get the most recent version of the file -- ASSIGNED
940882 Consolidate waitForCondition implementations and switch to using BrowserTestUtils.waitForCondition -- NEW
958147 Choose one of run-if or skip-if and get rid of the other -- REOPENED
969334 mozinstall should not magically try to find the mount point of the DMG -- NEW
996652 Scope the private symbols of head.js -- NEW
1028895 Mouseover triggered in mochitest-browser & dt according to position of mouse cursor on test box -- NEW
1036328 Support bisection in case of timeout/crash -- NEW
1036934 Add test for content editing keyboard shortcuts -- NEW
1063706 User build phones that have the screen lock setting enabled cannot be reached with adb after a reboot after 15-20 seconds - find a way to determine this and notify the user -- NEW
1072854 package.json after installing from an npm-mirror repository doesn't work with CommonJS require() -- UNCONFIRMED
1072912 Remove makefile targets for running tests from -- NEW
1078894 Create example test of do_await_remote_message -- NEW
1080806 Port to use mozbase -- NEW
1086570 Don't hardcode urls in the report html as they can vary from suite to suite -- NEW
1121710 Fix MenuBar class for correct handling of menus -- NEW
1124746 create a script when tells us if we have confidence that the regression we see includes all related regressions/improvements -- NEW
1125863 Reports should differentiate enabled from added and disabled from removed -- NEW
1132057 [mozlog] HTML log should show the passed/failed tests on the top of the page as default -- NEW
1137691 SpecialPowers.getFocusedElementForWindow is misnamed -- NEW
1143908 Switching to frame by element should accept element reference instead of UUID P3 NEW
1143928 Refactor Deck and Panel classes to reduce code duplication -- NEW
1151035 add ability to ouija to generate a report of builders and orangeness - including ones that go above or below a threshold -- NEW
1164443 Mozinstall should only install in an empty dir P1 NEW
1166431 Create distinct log files for each call to BaseMarionetteTestRunner.run_tests P3 NEW
1176474 Mozregui: Add some tests -- NEW
1177336 mozfile.remove uses excessive system calls -- NEW
1191446 Create a mach command for rerunning failed jobs on a previous push using new code -- NEW
1192866 Throw an exception when a non-top-level window is passed to synthesizeKey -- NEW
1196305 [Qb] multiple groupby should string-join multiple columns, the aggregate? -- NEW
1199700 add feature to make collecting nspr logs easier in reftest -- NEW
1218554 [mozinstall] Failure during install on OS X: "local variable 'appDir' referenced before assignment" -- NEW
1229089 Stop pre-processing reftest.js -- NEW
1247149 mozscreenshots: Support restricting configurations in sets -- ASSIGNED
1258664 Add more details about which chrome window handles are leaked in tearDown of a FirefoxTestCase -- NEW
1273498 Update Puppeteer classes for MetaClass -- NEW
1283216 Allow Marionette client object to be constructed with the build from the local environment as the default P3 REOPENED
1286894 Enable Treeherder to add new TC jobs for non try repositories -- NEW
1295617 [marionette harness tests] Improve display of test ids for parametrized tests P5 NEW
1298803 Add test to quit Firefox via a shortcut -- REOPENED
1298900 [marionette harness tests] Improve readability of tests/fixtures using `num_fails_crashed` P5 NEW
1311429 Reftest harness should use mozcrash.kill_and_get_minidump -- NEW
1315704 [marionette harness tests] Test that BaseMarionetteArguments constructs arguments as expected P5 ASSIGNED
1317782 Running twice fails to set up Buildbot -- NEW
1337013 Make gtest mach command invoke -- NEW
1354458 Get rid of `self.wait_for_condition()` in favor of `Wait().until()` P3 ASSIGNED
1364349 Remove `Puppeteer.platform` wrapper in favor of `marionette.session_capabilities['platformName']` -- ASSIGNED
1368034 Update default values for urlbar searches in Marionette P3 ASSIGNED
1374827 Remove em:unpack from the mozscreenshots extension -- ASSIGNED
1376672 Intermittent TestSwitchWindowChrome.test_switch_tabs_for_new_background_window_without_focus_change | AssertionError: u'about:blank' != '' -- NEW
1388018 [mozfile] Add support for Python 3 -- ASSIGNED
1389488 addon.install should check if path of extension exists for a better error message P3 NEW
1393831 pointerMove action calculates wrong default element centre point P3 NEW
1397417 [tracking] Convert mozbase unittests to pytest -- NEW
1397849 Enable py2 and py3 linter on testing/mozbase -- ASSIGNED
1397853 Enable py2 and py3 linter on testing/mochitest -- ASSIGNED
1399158 add a --jsdebugger option to geckodriver P5 NEW

60 Total; 60 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