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 17:22, 10 August 2007

8,705 bytes added ,  10 August 2007
no edit summary
No edit summary
Line 28: Line 28:
* Checked similar things and all seemed ok
* Checked similar things and all seemed ok
* Major Software Update dialog box doesn't look as polished as en-US
* 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 194: Line 198:
*** 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:
* Scenario 3:
Line 251: Line 256:


'''fr'''
'''fr'''
'''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:
** 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:
** 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.
 
'''jp'''
'''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]
Marcia
canmove, Confirmed users
7,108

edits

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