MozillaWiki

Firefox:1.5.0.x:TBMajor Update 1.5.0.x to 2.0.0.x:Test Results:15012: Difference between revisions

Page Discussion

Firefox:1.5.0.x:TBMajor Update 1.5.0.x to 2.0.0.x:Test Results:15012 (view source)

Revision as of 02:01, 11 August 2007

12,345 bytes added ,  11 August 2007
→‎Bugs Discovered during Testing
 
(17 intermediate revisions by 5 users not shown)
Line 24: Line 24:
* Software Update History showed successful update entry
* Software Update History showed successful update entry
* Fallback update (after a forced failure) worked as well.
* Fallback update (after a forced failure) worked as well.
'''es-ES''' - '''PASS'''
* Checked similar things and all seemed ok
* Major Software Update dialog box doesn't look as polished as en-US
'''ja-jp-mac''' - '''PASS'''
'''fr''' - '''PASS'''


= Mac (PPC) - marcia =
= Mac (PPC) - marcia =
Line 45: Line 53:
* From version 1.5.0.12 (20070509) to version 2.0.0.6 (20070728)
* From version 1.5.0.12 (20070509) to version 2.0.0.6 (20070728)


= Windows XP - Tomcat, stephend, marcia, TimK =
= Windows XP - Tomcat, stephend, marcia, TimK, whimboo =
==stephend test results==
==stephend test results==
'''en-US''' - '''stephend'''
'''en-US''' - '''stephend'''
Line 80: Line 88:


==marcia test results==
==marcia test results==
*All '''PASS''' except for mismatch issue noted.
*en-US (marcia)
*en-US (marcia)
* Build-id:  
* Build-id:  
Line 89: Line 98:
* 1.5 profile with mozilla.com IMAP
* 1.5 profile with mozilla.com IMAP
* Tested composing mail to send offline. Don't send it, but wait until after upgrade to send. I did get the dialog prompt to send the mail, but I get a mail relay error when the mail tries to be sent.
* Tested composing mail to send offline. Don't send it, but wait until after upgrade to send. I did get the dialog prompt to send the mail, but I get a mail relay error when the mail tries to be sent.
*fr (marcia)
* Build-id: versione 2.0.0.6 (20070728)
* 1.5 profile with mozilla.com IMAP and POP3
* Filed https://bugzilla.mozilla.org/show_bug.cgi?id=391785 during this test cycle
==whimboo test results==
en-US (whimboo)
* Build-id: Gecko/2007072817 Thunderbird/2.0.0.6
* Compared original 2.0.0.6 application folder with MU application folder - no missing or remaining files.
* tested update while files are in use. inifinitly restart: bug 340535 happens
== Tomcats Test Results ==
*en-US (tomcat)
* Build-id:
* 1.5 profile with mozilla.com IMAP and yahoo pop
* Tested some Extensions and Mail profiles with mails and newsgroups and all went as expected.
*de (tomcat)
* Build-id: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.6) Gecko/20070728 Thunderbird/2.0.0.6 Mnenhy/0.7.5.0 ID:2007072817
* 1.5 profile with mozilla.com IMAP and yahoo pop
* Tested some Extensions and Mail profiles with mails and newsgroups and all went as expected.
*de (tomcat)
* Build-id: tested on mac - ppc
* 1.5 profile with mozilla.com IMAP and yahoo pop
* Tested some Extensions and Mail profiles with mails and newsgroups and all went as expected.


= Windows Vista - abillings, marcia =
= Windows Vista - abillings, marcia =
Line 109: Line 145:
* mozilla.com POP3
* mozilla.com POP3
* From version 1.5.0.12 (20070509) to version 2.0.0.6 (20070728)
* From version 1.5.0.12 (20070509) to version 2.0.0.6 (20070728)


= Windows 98 marcia =
= Windows 98 marcia =
Line 166: Line 204:
*** Buttons that were added to the custom toolbar remained, however all other changes were set to defaults.
*** Buttons that were added to the custom toolbar remained, however all other changes were set to defaults.
*** Everything else was migrated and appeared the same as in 1.5.0.12
*** Everything else was migrated and appeared the same as in 1.5.0.12
*** Litmus testcases: test 12 failed due to above toolbar problem, all other tests PASS.
*** Litmus testcases: test 12 failed due to above toolbar problem, test 13 unclear due to below Update History issue, all other tests PASS.
*** Build ID reported in Update History is 2007071612
 
* Scenario 3:
** 1.5.0.12 (20070509) -> 2.0.0.6 (20070728)
** Update method: channel = releasetest, theme set to Black Japan (1.5 only)
** Date: 10 Aug 2007
** Results: PASS
** Notes:
*** Themes and Extensions that did not have 2.0 compatible versions were checked for updates and none were found.  This is expected behaviour.
*** Buttons that were added to the custom toolbar remained, however all other changes were set to defaults.
*** Everything else was migrated and appeared the same as in 1.5.0.12
*** Theme reverted to default theme with no warnings.  Reverting back to 1.5.0.12 restores Black Japan theme.
 
* Scenario 4:
** 1.5.0.12 (20070509) -> 2.0.0.6 (20070728)
** Update method: channel = releasetest, theme set to Pitch Dark (1.5/2 compatible)
** Date: 10 Aug 2007
** Results: PASS
** Notes:
*** Themes and Extensions that did not have 2.0 compatible versions were checked for updates and none were found.  This is expected behaviour.
*** Buttons that were added to the custom toolbar remained, however all other changes were set to defaults.
*** Everything else was migrated and appeared the same as in 1.5.0.12
*** Theme Pitch Dark still enabled after update.
 
* Scenario 5:
** 1.5.0.12 (20070509) -> 2.0.0.6 (20070728)
** Update method: channel = releasetest, theme set to Vista Mail (popular)
** Date: 10 Aug 2007
** Results: PASS
** Notes:
*** Themes and Extensions that did not have 2.0 compatible versions were checked for updates and none were found.  This is expected behaviour.
*** Buttons that were added to the custom toolbar remained, however all other changes were set to defaults.
*** Everything else was migrated and appeared the same as in 1.5.0.12
*** Theme Vista Mail still enabled after update.
 
* Scenario 6:
** 1.5.0.12 (20070509) -> 2.0.0.6 (20070728)
** Update method: channel = releasetest, theme set to Noia 2.0 eXtreme (popular)
** Date: 10 Aug 2007
** Results: PASS
** Notes:
*** Themes and Extensions that did not have 2.0 compatible versions were checked for updates and none were found.  This is expected behaviour.
*** Buttons that were added to the custom toolbar remained, however all other changes were set to defaults.
*** Everything else was migrated and appeared the same as in 1.5.0.12
*** Theme Noia 2.0 eXtreme still enabled after update.
 
* Scenario 7:
** 1.5.0.12 (20070509) -> 2.0.0.6 (20070728)
** Update method: channel = betatest
** Date: 10 Aug 2007
** Results: PASS
** Notes:
*** Themes and Extensions that did not have 2.0 compatible versions were checked for updates and none were found.  This is expected behaviour.
*** Buttons that were added to the custom toolbar remained, however all other changes were set to defaults.
*** Everything else was migrated and appeared the same as in 1.5.0.12
 
'''fr'''
* Scenario 1:
** 1.5.0.12 (20070509) -> 2.0.0.6 (20070728)
** Update method: channel = releasetest
** Date: 10 Aug 2007
** Results: PASS
** Notes:
*** Themes and Extensions that did not have 2.0 compatible versions were checked for updates and none were found.  This is expected behaviour.
*** Buttons that were added to the custom toolbar remained, however all other changes were set to defaults.
*** Everything else was migrated and appeared the same as in 1.5.0.12
 
* Scenario 2:
** 1.5.0.12 (20070509) -> 2.0.0.6 (20070728)
** Update method: channel = betatest
** Date: 10 Aug 2007
** Results: PASS
** Notes:
*** Themes and Extensions that did not have 2.0 compatible versions were checked for updates and none were found.  This is expected behaviour.
*** Buttons that were added to the custom toolbar remained, however all other changes were set to defaults.
*** Everything else was migrated and appeared the same as in 1.5.0.12
 
* Scenario 3:
** 1.5.0.12 (20070509) -> 2.0.0.6 (20070728)
** Update method: channel = releasetest, set theme to 1.5 only theme
** Date: 10 Aug 2007
** Results: PASS
** Notes:
*** Themes and Extensions that did not have 2.0 compatible versions were checked for updates and none were found.  This is expected behaviour.
*** Buttons that were added to the custom toolbar remained, however all other changes were set to defaults.
*** Everything else was migrated and appeared the same as in 1.5.0.12
*** Theme reverted to default theme after update.  Downgrading to 1.5.0.12 reverts the theme to the 1.5 only theme.
 
* Scenario 4:
** 1.5.0.12 (20070509) -> 2.0.0.6 (20070728)
** Update method: channel = betatest, set theme to 2.0 compatible theme
** Date: 10 Aug 2007
** Results: PASS
** Notes:
*** Themes and Extensions that did not have 2.0 compatible versions were checked for updates and none were found.  This is expected behaviour.
*** Buttons that were added to the custom toolbar remained, however all other changes were set to defaults.
*** Everything else was migrated and appeared the same as in 1.5.0.12
*** Custom theme still enabled after update.
 
* Scenario 5:
** 1.5.0.12 (20070509) -> 2.0.0.6 (20070728)
** Update method: channel = releasetest, ran litmus tests
** Date: 10 Aug 2007
** Results: PASS
** Notes:
*** Themes and Extensions that did not have 2.0 compatible versions were checked for updates and none were found.  This is expected behaviour.
*** Buttons that were added to the custom toolbar remained, however all other changes were set to defaults.
*** Everything else was migrated and appeared the same as in 1.5.0.12
*** Custom theme still enabled after update.
*** Build ID reported in Update History is 2007071612
*** Litmus testcases: test 12 failed due to above toolbar problem, test 13 unclear due to Update History issue, all other tests PASS.
 
'''de'''
* Scenario 1:
** 1.5.0.12 (20070509) -> 2.0.0.6 (20070728)
** Update method: channel = releasetest
** Date: 10 Aug 2007
** Results: PASS
** Notes:
*** Themes and Extensions that did not have 2.0 compatible versions were checked for updates and none were found.  This is expected behaviour.
*** Buttons that were added to the custom toolbar remained, however all other changes were set to defaults.
*** Everything else was migrated and appeared the same as in 1.5.0.12
 
* Scenario 2:
** 1.5.0.12 (20070509) -> 2.0.0.6 (20070728)
** Update method: channel = betatest
** Date: 10 Aug 2007
** Results: PASS
** Notes:
*** Themes and Extensions that did not have 2.0 compatible versions were checked for updates and none were found.  This is expected behaviour.
*** Buttons that were added to the custom toolbar remained, however all other changes were set to defaults.
*** Everything else was migrated and appeared the same as in 1.5.0.12


* Scenario 3:
* Scenario 3:
** 1.5.0.12 (20070509) -> 2.0.0.6 (20070728)
** 1.5.0.12 (20070509) -> 2.0.0.6 (20070728)
** Update method: channel = releasetest, theme set to Black Japan (1,5 only)
** Update method: channel = releasetest, set theme to 1.5 only theme
** Date: 10 Aug 2007
** Results: PASS
** Notes:
*** Themes and Extensions that did not have 2.0 compatible versions were checked for updates and none were found.  This is expected behaviour.
*** Buttons that were added to the custom toolbar remained, however all other changes were set to defaults.
*** Everything else was migrated and appeared the same as in 1.5.0.12
*** Theme reverted to default theme after update.  Downgrading to 1.5.0.12 reverts the theme to the 1.5 only theme.
 
* Scenario 4:
** 1.5.0.12 (20070509) -> 2.0.0.6 (20070728)
** Update method: channel = betatest, set theme to 2.0 compatible theme
** Date: 10 Aug 2007
** Date: 10 Aug 2007
** Results: PASS
** Results: PASS
Line 177: Line 358:
*** Buttons that were added to the custom toolbar remained, however all other changes were set to defaults.
*** Buttons that were added to the custom toolbar remained, however all other changes were set to defaults.
*** Everything else was migrated and appeared the same as in 1.5.0.12
*** Everything else was migrated and appeared the same as in 1.5.0.12
*** Theme reverted to default theme with no warnings.
*** Custom theme still enabled after update.
 
* Scenario 5:
** 1.5.0.12 (20070509) -> 2.0.0.6 (20070728)
** Update method: channel = releasetest, ran litmus tests
** Date: 10 Aug 2007
** Results: PASS
** Notes:
*** Themes and Extensions that did not have 2.0 compatible versions were checked for updates and none were found.  This is expected behaviour.
*** Buttons that were added to the custom toolbar remained, however all other changes were set to defaults.
*** Everything else was migrated and appeared the same as in 1.5.0.12
*** Custom theme still enabled after update.
*** Build ID reported in Update History is 2007071612
*** Litmus testcases: test 12 failed due to above toolbar problem, test 13 unclear due to Update History issue, all other tests PASS.
 
'''jp'''
* Scenario 1:
** 1.5.0.12 (20070509) -> 2.0.0.6 (20070728)
** Update method: channel = releasetest
** Date: 10 Aug 2007
** Results: PASS
** Notes:
*** Themes and Extensions that did not have 2.0 compatible versions were checked for updates and none were found.  This is expected behaviour.
*** Buttons that were added to the custom toolbar remained, however all other changes were set to defaults.
*** Everything else was migrated and appeared the same as in 1.5.0.12
 
* Scenario 2:
** 1.5.0.12 (20070509) -> 2.0.0.6 (20070728)
** Update method: channel = betatest
** Date: 10 Aug 2007
** Results: PASS
** Notes:
*** Themes and Extensions that did not have 2.0 compatible versions were checked for updates and none were found.  This is expected behaviour.
*** Buttons that were added to the custom toolbar remained, however all other changes were set to defaults.
*** Everything else was migrated and appeared the same as in 1.5.0.12
 
* Scenario 3:
** 1.5.0.12 (20070509) -> 2.0.0.6 (20070728)
** Update method: channel = releasetest, set theme to 1.5 only theme
** Date: 10 Aug 2007
** Results: PASS
** Notes:
*** Themes and Extensions that did not have 2.0 compatible versions were checked for updates and none were found.  This is expected behaviour.
*** Buttons that were added to the custom toolbar remained, however all other changes were set to defaults.
*** Everything else was migrated and appeared the same as in 1.5.0.12
*** Theme reverted to default theme after update.  Downgrading to 1.5.0.12 reverts the theme to the 1.5 only theme.
 
* Scenario 4:
** 1.5.0.12 (20070509) -> 2.0.0.6 (20070728)
** Update method: channel = betatest, set theme to 2.0 compatible theme
** Date: 10 Aug 2007
** Results: PASS
** Notes:
*** Themes and Extensions that did not have 2.0 compatible versions were checked for updates and none were found.  This is expected behaviour.
*** Buttons that were added to the custom toolbar remained, however all other changes were set to defaults.
*** Everything else was migrated and appeared the same as in 1.5.0.12
*** Custom theme still enabled after update.
 
* Scenario 5:
** 1.5.0.12 (20070509) -> 2.0.0.6 (20070728)
** Update method: channel = releasetest, ran litmus tests
** Date: 10 Aug 2007
** Results: PASS
** Notes:
*** Themes and Extensions that did not have 2.0 compatible versions were checked for updates and none were found.  This is expected behaviour.
*** Buttons that were added to the custom toolbar remained, however all other changes were set to defaults.
*** Everything else was migrated and appeared the same as in 1.5.0.12
*** Custom theme still enabled after update.
*** Build ID reported in Update History is 2007071612
*** Litmus testcases: test 12 failed due to above toolbar problem, test 13 unclear due to Update History issue, all other tests PASS.


= Focused Testing =
= Focused Testing =
Let's try to go through all of the tests in the major updates reference page and test around different kinds of profiles, containing multiple extensions and themes, compatible and incompatible with 2.0x. Keep an eye out for data loss problems, such as mail, labels/tags/settings, and any other preferences that should be preserved after an update.
Let's try to go through all of the tests in the major updates reference page and test around different kinds of profiles, containing multiple extensions and themes, compatible and incompatible with 2.0x. Keep an eye out for data loss problems, such as mail, labels/tags/settings, and any other preferences that should be preserved after an update.
= Bugs Discovered during Testing =
*[https://bugzilla.mozilla.org/show_bug.cgi?id=391785 Bug 391785]
*[https://bugzilla.mozilla.org/show_bug.cgi?id=391792 Bug 391792]
Marcia
canmove, Confirmed users
7,108

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/65132...65178"