QA/Firefox3/TestPlan/Addons

Feature Addons Test Plan

Overview

This Testplan will focus on the new components of Addons and FUEL 0.2 that will be included with Firefox 3.

1) Test Addons

Priority 1 items include:

• Unify add-ons management system and add plugin management system (bug 339056)
• Support shipping of localized user-facing Add-on text

priority 2 items include:

• Add-ons can be installed in fewer mouse clicks
• Ensure user understands the risks about installing extensions
• Clarify XPi install dialogs and user interactions
• Allow Add-on configuration UI to be accessed from main application configuration UI
• Improve discoverability of Add-on configuration UI
• Add visual indication to browser UI when Add-on updates are available
• Add permanent button for restarting Firefox (bug 369075)
• Simplify language and unify terminology related to Add-ons
• Support displaying information about the update in the updater
• [strike]Support add-on conflict resolution[/strike]
• Promote the existence of Add-ons that could help the user accomplish their current task
• Help documents should link to related Add-on categories on addons.mozilla.org

The following items are At Risk for this milestone.

• Remove extension installation whitelist (Help wanted)
• Install Add-on without requiring a browser restart

2) Test FUEL

• Ship the FUEL JavaScript library

Scope of planned testing

(What do you plan to test? What is covered by Developer testing? What is not practical to test?)

Coverage includes:

• Priority one feature test cases.

Platform and Configurations

( Describe any particular OS platform, environmental configurations or FireFox configuration considerations)

Major Test Areas

Plugins:

• Sorting of the plugins, including eliminating duplicate entries
• Selection/focus
  • Disable button on selection
  • Enable button on selection
• Restart button
• Find Updates button
• Vendor homepage link
• "Make compatible" functionality
• Edge cases, such as:
  • Disabling a plugin while it's running
    • Clicking refresh while in this state
  • Re-enabling, then refreshing
  • Ensuring that plugins stay enabled/disabled on restart
  • Any interaction with about:plugins
• Making sure to get broad coverage of plugins
  • (Get a list going, stephend!)

Schedule/milestones

( Provide some breakdown of the major areas of the feature, how long it will take to develop or run the tests, and an approximate time this will be done.

References

(List useful links to the bug containing design info, feature meeting notes, wiki info, standards info, litmus group or subgroup, etc)