Release Sign-off

Summary

The following is a document of processes and instructions for mobile QA understanding of Firefox for Android's post review sign-off on store availability via Google Play and any other mobile store. Any and all questions should be directed to the mobile QA lead for the release, QA-Mobile (irc: AaronMT), (irc: kbrosnan) or (irc: tchung).

Context

This document describes the vision for an ideal Firefox on Android sign off; code name Fennec and the key release themes that flow from that vision, in order of priority. This document will consist of a general release checklist Mozilla Mobile QA should use for releases. It will be organized by major functional activity in rough chronological order.

Android Release

Post build verification, it is the QA driver's responsibility to complete testing and map test results to a release-driver followup email notification. Upon release driver notice of the latest release uploaded to Google Play and any other mobile store, the following processes and instructions should be executed to ensure proper QA sign-off.

Verification of the Package Availabilty

• Verify that the newly updated Firefox package is available on Google Play and any other store that was the signed-off build was published to
  • Firefox (i.e., [1]), and Firefox Beta (i.e, [2])
• Verify that the newly updated Firefox package is available elsewhere.
  • Yandex Store is an application store available for Android installation. There is no public web-site.
    • Yandex is available for download on Android here: http://m.store.yandex.com/
      • An account is required in order to login and to download Firefox for Android
      • At this time, only Firefox, not Firefox Beta, is published on the Yandex Store

Note: It can take up to an hour for Google to propagate changes to the market reflecting availability of an updated package. It is the QA driver's responsibility to notify release-drivers if a change does not occur after this time.

Store Differentiation (Package Availability)

Verification of a Successful Clean Install

• Verify that your able to find and install both packages off the published stores either via device or through online interface
  • Upon installation, spot-check verify that the following performs as expected
    • Successful launch of the package installed
    • Successful uninstallation of the package installed through the available stores

Verification of a Successful Upgrade

• Verify that your able to successfully update your existing Firefox or Firefox Beta install by updating the package off the available stores either via device or through online portal interfaces. i.e, http://play.gooogle.com or http://m.store.yandex.com
  • Upon completion of the update, spot-check verify that the following items are preserved and functions performing as expected:
    • Language availability (check the L10N Dashboard)
      • Toggle device system language and check for language availability in-product (strings in content and in Java)
    • Preferences
    • Sync account settings
    • Add-ons and add-on state
    • Web Applications
    • Bookmarks and history, reading list
    • Successful uninstallation of the package installed through the available markets

Post Verification

• Post verification, it is the QA driver's responsibility to send a follow-up email notification to release-drivers <release-drivers@mozilla.org> dialoging any success or failures. Upon successful verification results; this will yield completion of a given release. The last step is completed.

Store Differentiation