The team focuses on testing current and upcoming releases of Firefox. Some of our responsibilities include qualifying builds prior to a maintenance or milestone release. Some of the responsibilities include, but are not limited to:
- Verifying bugs using a triage strategy
- Running basic functional tests and smoke tests - automated and manual
- Running our automated test suites on localized builds
- Running automated update tests across platforms, through all update paths, across localized builds
- Making sure web content is ready for consumption
In addition to qualifying builds prior to a release, we perform ongoing tasks on the development branches to ensure no major problems get uplifted as we merge changes to the next branch. For example, on a daily basis we:
- Confirm new unconfirmed bugs
- Verify bugs on development branches like Aurora and Beta
- Engage community and new volunteers in helping improve Firefox through test day events
- Interact with developers to help them test the features they implement
- Perform exploratory testing on new features while on the Aurora branch
- Write test cases in Litmus for new features
- Monitor crash-stats to assess stability
- File and track new crasher bugs as they appear in crash-stats
- Manage web compatibility testing through community involvement or crowdsourcing companies that help in testing hardware configurations and top-site testing
All of which help assess the quality of individual new features as well as the Firefox version as a whole.
The team is lead by Juan Becerra who coordinate testing of their respective areas among several MoCo employees and community volunteers. Traditionally new features are tested by several MoCo QA employees, while maintenance releases are tested by Al and a handful of people depending on availability. Anyone is welcome and encouraged to participate.
Team Members and Assignments
8:30am PDT, every Wednesday QA/Desktop_Firefox/StaffMeetings
Security Triage Team
The primary purpose of this team is to verify security fixes for Firefox releases. If you want to be someone who is committed to helping with security fix verification during the Beta release cycle, please add your name below. If you are interested in being part of this team but don't have the skills or bugzilla access, please contact Anthony Hughes.
Release test plans
Anyone can participate. There are several ways in which YOU can participate: