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

From MozillaWiki
Jump to navigation Jump to search
Line 37: Line 37:
*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 set to incompatible.
*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 set to incompatible.


== Test Cases (supposing implementation lands on Firefox 10) ==
== Test Cases ==
 
An add-on can have different states in a Firefox version: compatible-incompatible, enabled/disabled, pending restart, updated/in need of update.
 
[https://docs.google.com/spreadsheet/ccc?key=0Amty6gb0hLqVdDR6NlMxYWJoSzZSbEx3VTNnWk02Vmc&hl=ro#gid=0 test cases]


*Install several add-ons (binary component, blacklisted) on Firefox 9
*Install several add-ons (binary component, blacklisted) on Firefox 9

Revision as of 16:23, 7 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 Waiting for implementation

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.

Reference

  • Feature wiki page - Link
  • There are no RESOLVED bugs on Add-on Manager side. All bugs are still New or Assigned.
  • Two bugs are RESOLVED on AMO: 692971 692972

Use Cases to Test

  • User installs several types of add-ons on a Firefox version.
  • 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 set to incompatible.

Test Cases

An add-on can have different states in a Firefox version: compatible-incompatible, enabled/disabled, pending restart, updated/in need of update.

test cases

  • Install several add-ons (binary component, blacklisted) on Firefox 9
  • Upgrade To Firefox 10.
    • Blacklisted and Binary components Add-ons should be set to incompatible after upgrading.
    • Other add-ons should be set to compatible automatically
  • Install several add-ons (binary component, blacklisted) on Firefox 4
  • Manually Upgrade successively with 1 unit,from Firefox 4 up to Firefox 10 (going through F5,6,7,8,9)
    • Blacklisted and Binary components Add-ons should be set to incompatible in Firefox 10.
    • Other add-ons should be set to compatible automatically.
  • Install add-ons that have MinVersion>Firefox10 on Firefox 9.
  • Manually upgrade to the following version-Firefox10 (MinVersion should be greater than this version)
    • These add-ons should still be listed as incompatible after the installation.

Important bugs

Retrieved from "https://wiki.mozilla.org/index.php?title=Features/Add-ons/Add-ons_Default_to_Compatible/TestPlan&oldid=365776"