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

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 1509->2001.

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)

Basic Tests

Currently we have a testing environment setup that allows us to test major updates end to end. Download a released 1509 build, install it, and edit the channel-prefs.js file so that the release channel is set to "releasetest". After restart:

• Check for updates and make sure a major update is offered.
• Check the major update in-line details page.
• All links within the details page should open in a new browser window.
• "Later" should dismiss the dialog.
• "Never" will dismiss the dialog, and from then on it should not pop up automatically prompting you for a major update.
• "Get the new version" will take you to a dialog prompting you to accept the EULA.
• Read the EULA and check for obvious errors.
• All links within the EULA should open in a new window.
• "Cancel" should take you out of the dialog.
• Only by agreeing to the EULA should you be able to continue.
• "Continue" should go ahead and download the major update.
• Click on "Details" link, "Pause" (and then "Resume"), and "Hide" buttons and make sure they behave as they would in any other software update. Back button is disabled and it is a known bug.
• "Restart" the application once the update is finished and make sure you end with a 2.0.0.1 installation.
• At this point you should have an installation identical to what you would get if you installed 2.0.0.1 by itself. Currently Windows and Mac leave a couple of files behind and there's a bug already filed.

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

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 2.0.0.1 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)