Firefox:1.5.0.x:Tbird Major Update TestDay1.5.0.x to 2.0.0.x
This is a plan for testing Thunderbird 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->2006.
At a basic level we should:
- Make sure updates are presented
- Make sure the in-line content for Details and EULA is localized (at this point this is in question, localized pages not ready)
- Make sure the user profile is preserved after the major update
- Make sure updates don't break basic functionality for user (ability to read/write/check mail, add feeds, and such)
Accounts
Test mail account information is at https://intranet.mozilla.org/QA:IMAP/POP_Mail_test_accounts. Please make an IT Request if you need an additional pair of accounts for testing. Existing accounts are all assigned.
Setup
- Some things to pre-populate in the 1.5 profile:
- Newsgroups
- Regular, password-protected, and SSL (which is independent of the former two)
- For SSL, use 'news.motzarella.org' with port 563 (just check the "Use Secure Connection (SSL)" box)
- Regular, password-protected, and SSL (which is independent of the former two)
- Flags/labels (both POP3 and IMAP)
- Column ordering (you can drag and drop)
- Layout views
- Customized toolbar buttons/sets
- Preferences such as composing in HTML/plaintext
- LDAP addressing config settings (ensure they migrate)
- Address books
- Cards
- Mailing Lists
- Filters
- Saved searches (per Asa!)
- Newsgroups
Basic Tests
Instructions For Triggering a Major Update Fx 15012->Fx2006:
- Download a released Fx15012 build from here: http://releases.mozilla.org/pub/mozilla.org/thunderbird/releases/1.5.0.12/
- Install it, and then change the update channel to releasetest in the channel-prefs.js file found in C:/Program Files/Thunderbird/defaults/pref/channel-prefs.js (this may differ in Vista machines)
-
pref("app.update.channel", "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!
Things to Check:
- Check for updates and make sure a major update is offered.
- Check the major update in-line details page. It should be translated for all locales.
- 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. EULA's will default to en-US versions.
- 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.6 installation.
- At this point you should have an installation identical to what you would get if you installed 2.0.0.6 by itself. Currently Windows and Mac leave a couple of files behind and there's a bug already filed.
- Check the Update history in the preferences and make sure it looks correct.
Extended Tests
We have to perform the same tests with 1.5.0.12 user profiles containing mail in different accounts, rss feeds, newsgroups, saved passwords, preferences, 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.
- Install extensions and themes that are not compatible with 2.0.x and some that are, for example (on Windows):
- Extensions:
- 1.5/2
- Contacts Sidebar - https://addons.mozilla.org/en-US/thunderbird/addon/70
- 1.5 Only
- Popular
- 1.5/2
- Themes:
- 1.5/2
- 1.5 only
- Black Japan - https://addons.mozilla.org/en-US/thunderbird/addon/1665
- Popular
- VistaMail - https://addons.mozilla.org/en-US/thunderbird/addon/4472
- Noia 2.0 eXtreme - https://addons.mozilla.org/en-US/thunderbird/addon/1947
- When you check for updates you should get a warning within the Major Update Dialog window and a button to list the incompatible extensions. If you continue and restart you will get a dialog on startup prompting you to check if there are updates to those incompatible extensions.
- Select the option to check for extension updates and then for installation. Your extensions should be updated and Thunderbird 2.0.0.6 should start without a problem.
- Extensions:
- Modify app.update.interval and set it to 60 (seconds). Modify app.update.timer and set it to 600 (milliseconds). (Preferences/Advanced/Config)
- Check for major updates and select "Later." The dialog will then pop up one minute later giving you the option for a major update.
- Check for major updates and select "Never." Wait more than one minute and check that the major update dialog does not pop up again automatically.
- Check for major updates manually after selecting "Never" and check that you get presented with a major update.
- After a major update go to Options(Preferences)/Advanced/Updates "Show History Status" and check that the update history information is correct.
- Try a forced-failure update, by editing the update.status file to say failed after detecting and downloading a major update.
Reference
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 - For Firefox): http://www.chevrel.org/mozco/20migration/display.php
This is a list of more in-depth tests spun off the Firefox Revised Software Update test cases in Litmus, under the Major/Minor Eula UI Functionality
These can be used for reference while testing Tbird major updates. A subset of these tests was created in Litmus, for Thunderbird, and it can be found here Litmus tests for Thunderbird Major Updates
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)
