Auto-tools/Automation Development< Auto-tools
!!! OUTDATED: Please be aware that the Automation Development team has been transitioned into Mozilla QA. Therefore the new team page can be found at https://wiki.mozilla.org/QA/Automation !!!
What is our Goal?
The Automation Development Crew seeks to improve Mozilla product quality by directly crafting automated tests as well as by teaching others to craft these tests and by creating an environment in which the skills of automated test writing can be practiced and honed.
Every one of us is part of the ultimate reservoir of automation knowledge. That means that we will always have an answer for your automation requests, whether those would apply to already existing test harnesses or necessary new ones. This page will give you information about our current projects and activities.
Currently we are covering the following harnesses:
|Mozmill||A harness for automating Gecko based applications from Firefox to Thunderbird.|
|Selenium||A web browser automation framework controlling the content render-able part of the browser.|
|Marionette||An automation driver (UI or internal JS) for Boot2Gecko and Firefox desktop.|
Meetings / Events
We have a public team meeting in irregular intervals. If you want to join the meetings, please check the meetings page for details.
The automation development team is a group of passionate and open minded people working on automation. We are spread around the world, but we have one collective goal to empower automation even more in the Mozilla project. If you want to get in contact with one of us please check the table below for more information.
|Dave Hunt||United Kingdom||davehunt|
Some of our projects can be accomplished in a short time while others will take longer, even several months. The prioritized projects reflect the most important projects in the current quarter and include the appropriate tasks which have to be fulfilled during that time. Other active projects have lower priority.
Firefox UI Tests
|Automation Training||-||Provide automation training to larger community through 4 automation training events|
|Documentation||Wiki||Establish the team presence across websites (Wiki, MDN) and improve the documentation to increase collaboration with the test automation community|
|Infrastructure||Puppet||Building up and maintaining the infrastructure for automation tasks|