Features/Add-ons/Add-ons Default to Compatible/TestPlan: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 5: Line 5:
| Feature  
| Feature  
| Status  
| Status  
| Direct Responsible
| Lead engineer
| QA Lead  
| QA Lead  
| Status
| Status
Line 11: Line 11:
| Add-ons Default To Compatible  
| Add-ons Default To Compatible  
| {{StatusHealthy|status=In Progress}}  
| {{StatusHealthy|status=In Progress}}  
| Lawrence Mandel
| Blair McBride
| Virgil Dicu  
| Virgil Dicu  
| {{StatusHealthy|status=In Progress}}  
| {{StatusHealthy|status=In Progress}}  

Revision as of 10:54, 16 November 2011

Silent Update Add-ons Default To Compatible

Feature Status Lead engineer QA Lead Status
Add-ons Default To Compatible In Progress Blair McBride 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

Non-Goals

  • Will not be tested:
    • Add-ons individual functionality after being enabled to default.

Fixed bugs in need of verification

Status-week 11/7/2011-11/14/2011

Implementation work has started on Add-on manager side starting with the following bugs:

TO DO list:

  • create 75% basic functionality test cases
  • run feature basic functionality test cases on all platforms (Windows XP, Windows 7, Mac OS 10.6, Ubuntu 11.10)
  • run feature basic functionality test cases on Firefox 7, 8 and 9, while upgrading from each one to Nightly.
  • create test cases for edge areas and different add-on states.

Status-week 11/15/2011-11/22/2011

Latest feature implementation:

TO DO list:

  • create and run test cases for recently implemented bugs
  • provide help for 18 November test day exploratory testing around Add-ons Default to compatible:Testday
  • follow-up on issues found in previous week

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

Signed-off for Aurora

Signed off for Aurora:

  • No major or critical bugs found
  • Feature's basic functionality test cases work as expected
  • Add-on are enabled and working after update

Sign-off Criteria for Release

  • No unresolved major or critical bugs
  • Feature's basic functionality test cases work as expected
  • Ensure users can upgrade their add-ons successively from one Firefox version to another without any unnecessary change of states (e. g. from disabled to enabled)
  • No other issues are triggered by this feature implementation
Retrieved from "https://wiki.mozilla.org/index.php?title=Features/Add-ons/Add-ons_Default_to_Compatible/TestPlan&oldid=370025"