The team focuses on testing current and upcoming releases of Firefox on Android. 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 - mostly manual; but automated in the near future
- Running our manual test suites on localized builds
- Making sure web content is viewable, acceptable and ready for consumption in Firefox for Android
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 Moztrap 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 different Android device 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 both Kevin Brosnan and Aaron Train who coordinate testing of their respective areas among several MoCo employees and community volunteers. Traditionally new features are tested by several MoCo QA employees. Anyone is welcome and encouraged to participate.
Team Members and Assignments
|Aaron Trainemail@example.com||MoCo Employee (full time)||Lead - New features testing coordination.|
|Kevin Brosnanfirstname.lastname@example.org||MoCo Employee (full time)||Lead - New features testing coordination.|
|Marc Schiferemail@example.com||MoCo Employee (full time)||Manager|
QA Current Release Test Plans
|Project Test Plan||Description||Scope||Timeframe|
|Firefox for Android 31||QA activities revolving around Firefox Aurora in the time frame for Firefox 31 final release.||Features in Firefox for Android 31||Upcoming Releases|
|Firefox for Android 32||QA activities revolving around Firefox Nightly in the time frame for Firefox 32 final release.||Features in Firefox for Android 32||Upcoming Releases|
|Firefox for Android 33||QA activities revolving around Firefox Nightly in the time frame for Firefox 32 final release.||Features in Firefox for Android 33||Upcoming Releases|
|Feature Ownership||Testing, Planning, and Bug Triage of new and stable Firefox features used till Firefox for Android 30|
Anyone can participate. There are several ways in which YOU can participate:
- File bugs
- Triage bugs (confirm existing bugs and assign them to the right buckets)
- Help test new features
- Write test cases
- Plan new features testing
- Help others who want to get involved.
How You Can Contact Us
If you're interested in helping out with anything below (or want to help with something else), please contact us. We hang out on irc.mozilla.org in the channel #qa.
- Mailing Lists
Download Firefox for Android
The easiest and most simplest way to help us by using Firefox for Android. One can download Firefox for Android on Google Play and installing it on your Android device.
- This is a list of all the features being considered for development across products in the near future: https://wiki.mozilla.org/Features.
- To be specific this is the list of potential mobile Firefox features being considered.
- You can find a list of features to be shipped in the coming milestones: https://wiki.mozilla.org/Firefox/Flight_Tracking