Confirmed users
414
edits
| Line 167: | Line 167: | ||
*** 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, all other tests PASS. | ||
* 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. | |||
= 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. | ||