Features/Add-ons/Add-ons Default to Compatible/TestPlan: Difference between revisions
Jump to navigation
Jump to search
Line 47: | Line 47: | ||
*Upgrade and verify that installed third party and restartless add-ons are default to compatible or incompatible if binary/blacklisted/strictCompatibility listed | *Upgrade and verify that installed third party and restartless add-ons are default to compatible or incompatible if binary/blacklisted/strictCompatibility listed | ||
*Upgrade and check behavior for add-ons installed on older Firefox versions | *Upgrade and check behavior for add-ons installed on older Firefox versions (<Firefox 7) | ||
*Upgrade from Firefox4 successively to Firefox 5,6,7,8,9 and 10 and verify that all add-ons are listed as expected. | *Upgrade from Firefox4 successively to Firefox 5,6,7,8,9 and 10 and verify that all add-ons are listed as expected. | ||
Revision as of 10:06, 8 November 2011
Silent Update Add-ons Default To Compatible
Feature | Status | Direct Responsible | QA Lead | Status |
Add-ons Default To Compatible | In Progress | Lawrence Mandel | Virgil Dicu | In Progress |
Summary
- As majority of add-ons work from one version to the next without the need for developer maintenance, Firefox will mark addons compatible with new versions of Firefox by default, except for the following:
- All binary add-ons
- All strict incompatible add-ons
- All blacklisted add-ons
- The Feature is planned for Firefox 10. Implementation has started on Firefox 10
The feature can be enabled by setting the "extensions.strictCompatibility" preference to false in about:config.
Reference
- Feature wiki page - Link
- Feature implementation has started on Add-on Manager side: bug 693901,bug 693899,bug 693897.
Status-week 1 beta
Use Cases to Test
- An add-on can have different states in a Firefox version: compatible-incompatible, enabled/disabled, pending restart, updated/in need of update.
- User installs several types of add-ons on a Firefox version with one or more of the above mentioned states
- When upgrading to a new version, Firefox will automatically set his add-ons to compatible with the new Firefox version, unless the installed add-ons are binary, blacklisted or strictly set to incompatible with the Firefox version.
Edge cases
- Upgrade and verify that installed third party and restartless add-ons are default to compatible or incompatible if binary/blacklisted/strictCompatibility listed
- Upgrade and check behavior for add-ons installed on older Firefox versions (<Firefox 7)
- Upgrade from Firefox4 successively to Firefox 5,6,7,8,9 and 10 and verify that all add-ons are listed as expected.
Test Cases
Test cases based on this feature are listed in the following spreadsheet: Link
Important bugs
- Tracking bugs:
- Add-on Manager: Bug 692664
- AMO: Bug 691834
Sign-off Criteria
- No unresolved major or critical bugs
- Feature's basic functionality test cases work as expected
- Ensure add-on individual functionality works normally after upgrading