QA/Firefox 3.next/Test Plan:AddonsManagerRedesign
- 1 Add-ons Manager Redesign
- 2 Feature Release Readiness Assessment
- 3 Feature Documentation
- 4 Feature Bug Management
- 5 Feature Test Items
- 6 Feature Tests
- 7 Community Test Events
- 8 Feature Documentation Details
- 9 Feature Release Readiness Assessment Details
- 10 Feature Bug Management Details
- 11 Feature Test Items Details
- 12 Feature Tests Details
- 13 Community Test Events Details
Add-ons Manager Redesign
|Development Status:||In progress (10/06/09)|
|Feature Testing:||In progress (10/06/09)|
|Team:|| By group:
|Tracking Bugs||By sub-project:|
This redesign will substantially improve the basic functionality of the a add-ons manager, such as installation and configuration of add-ons, as well as incorporate additional features and functionality, such as use of Personas and Jetpacks. The design will also remove parts of the manager that interrupt and distract user tasks.
The table below provides a top level go/no go assessment of whether the feature is release ready for the given milestone. Each milestone link references a section below that discusses the criteria and evaluation that went into the QA go/no-go decision.
|#Beta1||Ready to Ship|
|#Project_Wiki||Wiki Links to all feature related entries|
|#Developer_Links (blogs)||Developer links to feature related sites|
|#Other_Docs||Web links to feature related sites|
|#Developer_QA_Review||Details from developer and qa discussions regarding feature test strategies and issues.|
|#Bug_Tracking||Top level bugs tracking feature|
|#Bug_Verification||Feature bugs that need verification|
|#Bug_Triage||Links triage bug tasks|
The table below provides a breakdown of all feature items that should be covered and how they will be tested. Not all items will be covered by internal QA team members. It is important to list what should be covered. If it is not covered, list it as not covered.
Note: not all items listed below will apply for a given feature
|Test Item||Description||Covered By||Status|
|Item 1||Item 1 Description||Developer Tests|
|Item 2||Item 2 Description||Beta tester exposure|
|#Topsites||Top internet sites compatibilities|
|#Developer_Tests||Links to automated developer tests|
|#Mozmill_Tests||Links to automated mozmill feature test cases|
|#Smoke_Tests||link to smoke tests|
|#Regression_Tests||link to BFT and/or regression tests|
|#Functional_Tests||link to FFT and/or complete functional tests|
|#Testdays||Links to test day event results for feature|
|#Bugdays||Links to bug day event results for feature|
|#Meetups||Links to Meetup events for feature|
- Add-ons Manager Redesign
- Extension Manager API rewrite
- Discovery Pane
- Add-ons Compatibility Reporter
- Pull more AMO Data into the Add-ons Manager
- [10/05/27] Support for dropping XPI files into the extension install locations might be going away
- [10/05/10] Frontend Updates
- [10/04/29] The new Add-ons Manager is here
- [10/04/27] Frontend Updates
- [10/04/13] Frontend Updates
- [10/04/01] Add-ons Manager Redesign Update
- [10/03/24] A New Front Door
- [10/03/22] Frontend Updates
- [10/03/19] How we’re breaking some extensions in the near future
- [10/03/14] Look Ma, no restarts!
- [10/03/12] Simplifying
- [10/01/07] Do we need extension dependencies?
- [09/12/03] Relocating Firefox’s Add-ons Manager
- [09/11/23] Redesigning Firefox’s Addons Manager
Developer QA Review
The QA person responsible for the feature should hold a formal interview with the lead developer or feature champion. Below are questions that should be asked in the interview:
- Do we have automated tests for the feature?
- What do they cover?
- What do they not cover?
- How well do they cover the feature?
- What are the important areas we should focus on?
- What are the dependencies?
- What is our comfort level with this feature in its current state?
- What feedback would you like from QA?
- Top level bugs tracking feature. Include any relevant bug queries that are helpful for tracking feature status.
|Add-ons Manager (interface and backend):|
|Add-ons Compatibility Reporter:|
|Pull More AMO Data into the Add-ons Manager:|
|Top Issues:||Open bugs which blocks testing of a specific area.|
- Bug triage information
- Details of feature localization test requirements
- Keyboard accessibility: Test that all actions can be performed through the keyboard, without the use of a mouse. Items can either be interacted with directly (buttons to perform actions, for example), or be accessed through a popup/context menu of any given item. Success is met when all interactive items can be tabbed to and all features are reachable through either an interactive control or the context menu of an item.
- Themeing testing: Is the UI still fully readable if the operating system's theme is changed to high-contrast, inverted colors etc? Success is met when all controls are still readable in interactive and noninteractive states when changing the operating system's color scheme.
- Screen reader exposure: Are all controls and items exposed with all available information to screen readers? Success is met when all controls speak with their name and control type (like button etc.).
- Details of plugins compatibility test requirements
- Details of addons compatibility
- Details of top internet sites test requirements
To test all of the new features which will come with Firefox 4 we have setup a test plan which can be found on Google Spreadsheets.
- Links to automated developer tests
If a particular feature needs manual tests which should also be covered by Mozmill tests please add the "[mozmill-test-needed]" whiteboard entry to the feature implementation or regression bug.
List of Mozmill Tests:
- Links to automated mozmill feature test cases
Areas which cannot be tested by our automated test harnesses will need a good set of manual tests on Litmus. We cover those tests in a Google Spreadsheet.
- links to litmus smoke tests or description
- links to litmus BFT and/or regression tests description
- links to litmus FFT and/or complete functional tests description