Confirmed users
1,477
edits
TestEngineering/UI/AMO/AddonUpdates: Difference between revisions
TestEngineering/UI/AMO/AddonUpdates (view source)
Revision as of 01:07, 8 February 2011
, 8 February 2011no edit summary
(Created page with "=Add-on Updates=<br> update.php is what Mozilla apps asks to see if there are add-on updates available. We have migrated it to Python and need to ensure that there are no regres...") |
No edit summary |
||
| Line 1: | Line 1: | ||
=Add-on Updates=<br> | =Add-on Updates=<br> | ||
update.php is what Mozilla apps asks to see if there are add-on updates available. We have migrated it to Python and need to ensure that there are no regressions.<br> | update.php is what Mozilla apps asks to see if there are add-on updates available. We have migrated it to Python and need to ensure that there are no regressions.<br> | ||
<br> | |||
=Settings=<br> | |||
To test the updates on the staging server we need to tweak the settings. | |||
<u>Settings for Firefox 3.6/4.0:</u> | |||
To test update on the staging server, change the following setting in your about:config <br>extensions.update.url to<br> https://addons.allizom.org/z/update?reqVersion=%REQ_VERSION%&id=%ITEM_ID%&version=%ITEM_VERSION%&maxAppVersion=%ITEM_MAXAPPVERSION%&status=%ITEM_STATUS%&appID=%APP_ID%&appVersion=%APP_VERSION%&appOS=%APP_OS%&appABI=%APP_ABI%&locale=%APP_LOCALE%&currentAppVersion=%CURRENT_APP_VERSION%&updateType=%UPDATE_TYPE%<br> <br><u>Settings for Fennec:</u> | |||
<br> To test update on the staging server, change the following setting in your about:config <br>extensions.update.url to<br> | |||
<br> https://addons.allizom.org/z/update?reqVersion=%REQ_VERSION%&id=%ITEM_ID%&version=%ITEM_VERSION%&maxAppVersion=%ITEM_MAXAPPVERSION%&status=%ITEM_STATUS%&appID=%APP_ID%&appVersion=%APP_VERSION%&appOS=%APP_OS%&appABI=%APP_ABI%&locale=%APP_LOCALE%&currentAppVersion=%CURRENT_APP_VERSION%&updateType=%UPDATE_TYPE% | |||
You need to restart Fennec after changing the update.url | |||
<u>Settings for Thunderbird:</u> | |||
To test update on the staging server, change the following setting in your about:config<br> extension.update.url to<br> <br> https://addons.allizom.org/z/update?reqVersion=%REQ_VERSION%&id=%ITEM_ID%&version=%ITEM_VERSION%&maxAppVersion=%ITEM_MAXAPPVERSION%&status=%ITEM_STATUS%&appID=%APP_ID%&appVersion=%APP_VERSION%&appOS=%APP_OS%&appABI=%APP_ABI%<br> <u><br>Settings for Seamonkey:</u><br> <br> To test update on the staging server, change the following setting in your about:config<br> extension.update.url to<br> <br> https://addons.allizom.org/z/update?reqVersion=%REQ_VERSION%&id=%ITEM_ID%&version=%ITEM_VERSION%&maxAppVersion=%ITEM_MAXAPPVERSION%&status=%ITEM_STATUS%&appID=%APP_ID%&appVersion=%APP_VERSION%&appOS=%APP_OS%&appABI=%APP_ABI%&locale=%APP_LOCALE%&currentAppVersion=%CURRENT_APP_VERSION%<br> | |||
<br> | <br> | ||
==Usecase Scenarios:== | |||
testcase 1: Update add-on versions | |||
Check that clicking on “Find updates”, lists the latest supported versions for your installed add-ons | |||
Ensure that the update is successful | |||
testcase 2: Update Firefox versions (with add-on updates) | |||
Install an older version of Firefox | |||
Install older versions of add-ons which are not supported on the version you are updating to.(pick one extension, theme,dictionary and a language pack | |||
Upgrade Firefox to a newer version | |||
Check that when Firefox starts, it prompts you to upgrade all your incompatible add-ons | |||
Ensure that the update is successful | |||
testcase 3:Update Firefox versions (with no add-on updates) | |||
Install an older version of Firefox | |||
Install the latest versions of add-ons(pick one extension, theme,dictionary and a language pack | |||
Upgrade Firefox to a newer version | |||
Check that when Firefox starts, there are no fake prompts for updates | |||
testcase 4:Update prompt while opening a Firefox profile | |||
Create a profile which has a few older versions of add-ons installed. | |||
Quit Firefox | |||
Start the firefox profile | |||
Check that there are updates for incompatible add-on versions | |||
testcase 5: Update prompt for beta add-ons | |||
Select an add-on which has multiple beta versions(say b1-b4) | |||
Install an older version of a beta add-on(b1 | |||
Tools-> Add-ons -->Click on “Find Updates” | |||
Check that b4 versions is listed as an update | |||
Update is successful | |||
testcase 6: Check that updates are only offered when the newer versions of the add-on are public | |||
Pick an add-on with an unreviewed latest version. | |||
Install the previous version of that add-on | |||
Tools-> Add-ons -->Click on “Find Updates” in the add-ons manager | |||
Check that there are no updates | |||
testcase 7: Check that there are no updates for unreviewed add-ons | |||
Pick an add-on with multiple unreviewed versions | |||
Install an older version | |||
Tools-> Add-ons -->Click on “Find Updates” | |||
No updates | |||
testcase 8: Check that no updates are offered if the newer version is incompatible with user's browser version/platform | |||
Pick an add-on with an incompatible latest version | |||
Install an older version and restart | |||
Tools-> Add-ons -->Click on “Find Updates” | |||
No updates are offered | |||
testcase 9: Check for platform compatibility | |||
Pick an add-on which has version (b-n) compatible with the test platform and version b not supported on your platform/OS | |||
Install version (b-n) and restart | |||
Tools-> Add-ons -->Click on “Find Updates” | |||
No updates are offered | |||
<br> <br> | |||