QA/Fennec: Difference between revisions
< QA
Jump to navigation
Jump to search
(→How you can contact us: Use canonical link) |
|||
| (4 intermediate revisions by 4 users not shown) | |||
| Line 3: | Line 3: | ||
* Verifying bugs using a triage strategy | * Verifying bugs using a triage strategy | ||
* Running basic functional tests and smoke tests | * Running basic functional tests and smoke tests; manual and automated | ||
* Running our manual test suites on localized builds | * Running our manual test suites on localized builds | ||
* Making sure web content is viewable, acceptable and ready for consumption in Firefox for Android | * Making sure web content is viewable, acceptable and ready for consumption in Firefox for Android | ||
| Line 10: | Line 10: | ||
* Confirm new unconfirmed bugs | * Confirm new unconfirmed bugs | ||
* Verify bugs on development branches like | * Verify bugs on development branches like Nightly and Beta | ||
* Engage community and new volunteers in helping improve Firefox through test day events | * Engage community and new volunteers in helping improve Firefox through test day events | ||
* Interact with developers to help them test the features they implement | * Interact with developers to help them test the features they implement | ||
* Perform exploratory testing | * Perform exploratory testing of new features on the Nightly branch | ||
* Monitor [http://crash-stats.mozilla.com/ crash-stats] to assess stability | * Monitor [http://crash-stats.mozilla.com/ crash-stats] to assess stability | ||
* File and track new crasher bugs as they appear in crash-stats | * File and track new crasher bugs as they appear in crash-stats | ||
| Line 44: | Line 43: | ||
|Lead - New features testing coordination. | |Lead - New features testing coordination. | ||
|- | |- | ||
|} | |} | ||
| Line 84: | Line 53: | ||
* Plan new features testing | * Plan new features testing | ||
* Help others who want to get involved. | * Help others who want to get involved. | ||
=== Download Firefox for Android === | === 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 [https://play.google.com/store/apps/details?id=org.mozilla.firefox Google Play] and installing it on your Android device. | The easiest and most simplest way to help us by using Firefox for Android. One can download Firefox for Android on [https://play.google.com/store/apps/details?id=org.mozilla.firefox Google Play] and installing it on your Android device. | ||
== How you can contact us == | |||
If you're interested in contributing or have any other question, get in touch on [[Matrix]]: | |||
* [https://chat.mozilla.org/#/room/#firefox-android:mozilla.org #firefox-android] on [https://chat.mozilla.org/#/room/#firefox-android:mozilla.org chat.mozilla.org] | |||
Latest revision as of 14:54, 14 April 2026
Overview
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; manual and automated
- 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 Nightly 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 of new features on the Nightly branch
- 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.
Team Details
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.
- Lead - Kevin Brosnan (:kbrosnan)
- Lead - Aaron Train (:aaronmt)
Team Members and Assignments
| Name | Contact | Availability | Project Assignments |
| Aaron Train | atrain@mozilla.com | MoCo Employee (full time) | Lead - New features testing coordination. |
| Kevin Brosnan | kbrosnan@mozilla.com | MoCo Employee (full time) | Lead - New features testing coordination. |
Community Contribution
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.
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.
How you can contact us
If you're interested in contributing or have any other question, get in touch on Matrix: