Firefox:1.5.0.x:Major Update 1.5.0.x to 2.0.0.x

From MozillaWiki
Jump to: navigation, search

This is a plan for testing major updates going from 150x to 200x. Users of the latest 150x should be presented with the option to do a major update. If they choose this option and agree to the license agreement, they should be updated to a version of 200x, to be specific 15012->2004.

At a basic level we should:

  • Make sure updates are presented
  • Make sure the in-line content for Details and EULA is localized
  • Make sure the user profile is preserved after the major update
  • Make sure updates don't break basic functionality for user (ability to bookmark, add feeds, and such)

Mozilla Partner distribution builds will NOT have a major update at this time. Users attempting to update will automatically fallback. Link to [Partners Update Test Plan]

Instructions For Triggering a Major Update Fx 15012->Fx2006:

pref("", "releasetest");
  • Restart the browser and select Check for Updates from the Help menu.
  • NOTE: This is for MU testing purposes only. Please do not modify any files if you are not actively testing with the Mozilla QA team. Thanks!

Basic and Extended Tests

Basic and Extended tests are now in Litmus. They are in the 1.5x - 2.0x Major Update testgroup and FX 1.5-2.0 Major Update - Basic Tests and FX 1.5-2.0 Major Update - Extended Tests subgroups in the Firefox 2.0 Catchall test run.

We have to perform the same tests with 15012 user profiles containing bookmarks, history, saved form data, saved passwords, feeds, extensions and themes compatible with 200x, and extensions and themes not compatible with 200x. Think of a typical 150x user profile. After the major update the user profile should be kept, and during the update, the extensions and themes should be checked for compatibility.

CJKT Tests

The matrix for CJKT tests is on Google Docs. The updates there need to be run in order to make sure that search and home page settings are preserved across updates.


As a reference we should take a look at the test cases already in Litmus. Follow the link bellow, and enter your test RESULTS here

Quick Reference for l10n update details pages (from Major Update dialog):

This is a list of more in-depth tests spun off the Revised Software Update test cases in Litmus, under the Major/Minor Eula UI Functionality

check Details and EULA description
check that you can only install if you accept license
check eulas and descriptions are localized (Paul K., send a list of those that are ready)
check major update works on different locales
check interface elements work, buttons, links, text selection, scrolling, closing
check "fallback" major updates (should there be a failure in the update download for example)
check uninstalling and going back to previous build
check only one type of update is presented at a time minor/major
check major updates if you have multiple profiles
check extension compatibility check
check theme compatibility check
check what tabs are default after you update.
check these start pages are localized as before.
check Windows bits are signed after major update.
post: check minors are presented to the upgraded users
post: check major updates are presented only to those using the latest 150x
post: check minor updates are presented for those users who said never
post: check 200x users are not presented a major
post: check majors a presented when user had said never, then manually checked for updates again (assuming major are once again available)
check to see what happens when one type of update has been downloaded and not applied, and another type of update is made available.
check to see if it is possible to download and say later and then regret and then install something better, like a major update.
check what is left over after a "diff" (currently some crumbs are left for Win and Mac and it has been captured in a bug)
check the state of the registry after a major update (and uninstall)