Canmove, confirm
7,810
edits
Changes
no edit summary
This page cover covers the strategy 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 licence agreement, they should be updated to a version of 200x.
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'''
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:
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]
<pre>
