Confirmed users
3,816
edits
Activity Map: Difference between revisions
Jump to navigation
Jump to search
→Automation
| Line 9: | Line 9: | ||
==Automation== | ==Automation== | ||
* | * Automated Test Framework Development | ||
** Desktop | ** Builder tests: leaktest, profile test, make check | ||
** Android | ** Desktop: mochitest, browser-chrome, reftest, xpcshell, gtest, c++ tests, javascript tests, mozmill | ||
** B2G | ** Android: all desktop, plus robo-cop | ||
** B2G: all desktop, plus emulator web API, Gaia UI tests, Gaia integration tests, Gaia unit tests | |||
** Underlying automation components: mozbase, marionette, mach (shared), breakpad, crash integration in tests, building symbols, mozharness (shared), mozpool, automatic power cycling for mobile devices | |||
* Automated Performance test Framework, mozmill-ci, mozmill-environments, jenkins build systems for b2g, selenium, webdriver W3C spec | |||
** Desktop: talos, multi-browser speed tests, eideticker | |||
** Android: talos, robo-check (a form of talos), eideticker | |||
** B2G: b2g-perf framework, eideticker | |||
* Internal Developer Web tools | |||
** TBPL | |||
** Datazilla | |||
** Orangefactor | |||
** Moztrap | |||
** Bughunter | |||
** Bugzilla.mozilla.org | |||
* Internal Developer tools | |||
** Mach | |||
** Bisect in the cloud (mozregression's next version) | |||
** Debugger interfaces (something I'd like us to do more of) | |||
** Pulse | |||
** Profiler integration | |||
** Code coverage analysis | |||
** Performance regression analysis | |||
** Test synchronization with W3C test repos | |||
* Automation/Code Quality | |||
** Sheriffing of the Trees | |||
** Developing and educating others on developing automated tests | |||
** General bugzilla.m.o bug triage policies and community building around the early bug life cycle | |||
* Release Engineering | * Release Engineering | ||