From MozillaWiki
< QA‎ | Fennec‎ | Milestones‎ | 6.0
Jump to: navigation, search

Fennec 6.0 Beta Test Plan


The goal of this Overall Test Plan is to lay out our testing strategy, determine who will own certain test areas and when they will do it and, finally, track the status. All of our releases are tested off of the "Fennec 6.0 Beta Catch-All Test Run" on the Litmus TCM. For more information about Fennec 6.0, take a look at the mobile team's Feature Planning page.

Project contacts

PM: Thomas Arend (tarend)
Dev Lead: Stuart Parmenter (stuart)
Build: John Oduinn (oduinn)
QA: Kevin Brosnan (kbrosnan)


  • Start Date: 7/05/2011
  • End Date: 8/16/2011

Bugs in Release

Build Location and IDs

  1. Go to the nightly builds folder in our ftp directory
  2. Go to the "latest-mozilla-beta" folder
  3. Download and install the candidate onto your Android phone/device

Features Enabled

Feature Status Owner

Test Areas


QA Task Person/Group How Often?
Smoketests Waverley Once

Lite verification tests (or smoketests) will be first run when the builds are ready. Tests are available on litmus under the Fennec 6.0 Test Suite. In any case of failure in any Smoketest, blockers need to be raised ASAP before proceeding to the BFTs.

Results details can be found in Waverley's results wiki.

BFTs for 6.0 Features

QA Task Person/Group How Often?
BFTs Waverley Once

BFTs are a more comprehensive set of litmus tests that cover functional testing of features that have landed on Fennec 6. Tests are available on litmus under the Fennec 6 Test Suite.

Results details can be found in Waverley's results wiki.

Crasher Triage

QA Task Person/Group How Often?
Crasher Triage mw22 / nhirata Daily

Socorro is Mozilla's primary web interface for triaging crash reports sent in by our user base. Due to the relatively large amount of changes coming in on a nightly basis, there is a need to check for crash reports coming in for every build. The owner of this task will triage through top crashers on a daily basis, file bugs if necessary and find steps to reproduce for those crashers if possible.

Device Compatibility

QA Task Person/Group How Often?
Device Compatibility AaronMT Once

As part of our testing strategy, we will want to verify device compatibility checking for regressions or major issues in Firefox by running through our compatibility criteria spreadsheet . Mobile users can also contribute towards device qualifying by submitting feedback via our untested device survey.

Website Compatibility

QA Task Person/Group How Often?
Website Compatibility Aaronmt Once

As part of our testing cycle we want to cover and include a general testing process that focuses on website compatibility with sites viewed in mobile Firefox. We want you to use mobile Firefox to assist us in identifying any noticeably major issues found in websites. Issues can range from pages that do not look right, layout and positioning problems, interactivity issues, font issues and pages that greatly differ from browser to browser and what you would expect. You can help us by completing a website exploration form here, and following the companion instructional test-plan.


QA Task Person/Group How Often?
Testday kbrosnan Once

To continue determining better quality metrics, we'll want to work with our community to find new bugs and performance/stability metrics through the use of a Testday once per cycle per channel (i.e. nightly and beta). The QA owner for this task will send announcements, create a testplan, moderate the channel and post results for the Testday. To see when the next testday is schedule, please take a look at the Test_Days wiki.