canmove, Confirmed users
2,398
edits
QA/Fennec: Difference between revisions
Jump to navigation
Jump to search
m
no edit summary
mNo edit summary |
|||
| Line 1: | Line 1: | ||
= 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 [[QA/Desktop_Firefox/Triaged_Bug_List|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 | ||
* Firefox | * 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 Litmus for new features | |||
* Monitor [http://crash-stats.mozilla.com/ 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 - [mailto:kbrosnan@mozilla.com Kevin Brosnan (:kbrosnan)] | |||
* Lead - [mailto:atrain@mozilla.com Aaron Train (:aaronmt)] | |||
== Team Members and Assignments == | |||
{| class="fullwidth-table" | |||
| style="background:#EFEFEF; width:30%" | '''Name''' | |||
| style="background:#EFEFEF; width:30%" | '''Contact''' | |||
| style="background:#EFEFEF; width:10%" | '''Availability''' | |||
| style="background:#EFEFEF; width:30%" | '''Project Assignments''' | |||
|- | |||
|Aaron Train | |||
|[mailto:atrain@mozilla.com atrain@mozilla.com] | |||
|MoCo Employee (full time) | |||
|Lead - New features testing coordination. | |||
|- | |||
|Kevin Brosnan | |||
|[mailto:kbrosnan@mozilla.com kbrosnan@mozilla.com] | |||
|MoCo Employee (full time) | |||
|Lead - New features testing coordination. | |||
|- | |||
|Naoki Hirata | |||
|[mailto:nhirata@mozilla.org nhirata@mozilla.org] | |||
|Moco Employee (full time) | |||
|Crash analysis, user feedback monitoring, | |||
|- | |||
|} | |||