Changes

*'''Make sure updates don't break basic functionality for user (ability to bookmark, add feeds, and such)'''

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:

*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.

We have to perform the same tests with 1509 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.

As a reference we should take a look at the test cases already in Litmus. Follow the link bellow, and enter your [http://wiki.mozilla.org/Firefox:1.5.0.x:Major_Update_1.5.0.x_to_2.0.0.x:Test_Results '''test results here''']

This is a list of more in-depth tests spun off the Revised Software Update test cases in Litmus, under the [http://litmus.mozilla.org/show_test.cgi?searchType=by_category&product_id=1&testgroup_id=38&subgroup_id=623 Major/Minor Eula UI Functionality]