QA/Firefox 3.next/Test Plan:AddonsManagerRedesign: Difference between revisions

From MozillaWiki
< QA
Jump to navigation Jump to search
 
(40 intermediate revisions by 4 users not shown)
Line 1: Line 1:
<small>[[QA/Firefox_3.next/Test_Plan|&laquo; Firefox 3.next TestPlan]]</small>
<small>[[QA/Firefox_4/Test_Plan|&laquo; Firefox 4 TestPlan]]</small>


= Add-ons Manager Redesign =
= Add-ons Manager Redesign =
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.


== Discovery Pane ==
{| class="fullwidth-table"
As a part of this redesign project the Discovery Pane has its own [[QA/Firefox 3.next/Test Plan:AddonsManagerRedesign/DiscoveryPane|testplan]].
! style="width: 40%" | '''Area'''
! style="width: 60%" | '''Details'''
|-
| '''Development Status:'''
| In progress (10/06/09)
|-
| '''Feature Testing:'''
| In progress (10/06/09)
|-
| '''Team:'''
| By group:
* Jennifer Boriss (UX)
* Dave Townsend, Blair McBride, Robert Strong, Ben Parr, Benedict Hsieh (Add-ons Manager)
* Justin Scott, Jeff Balogh (Discovery Pane)
* Brian King, David McNamara (Add-on Compatibility Reporter)
* Henrik Skupin, Marco Zehe, Raymond Etornam (QA)
|-
| '''Tracking Bugs'''
| By sub-project:
* [https://bugzilla.mozilla.org/show_bug.cgi?id=550048 Redesign Addons Manager UI]
* [https://bugzilla.mozilla.org/show_bug.cgi?id=461973 Extension Manager API Rewrite]
* [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&component=Discovery%20Pane&product=addons.mozilla.org Discovery Pane]
* [http://bugzilla.mozilla.org/show_bug.cgi?id=565930 Add-on Compatibility Reporter]
* [http://bugzilla.mozilla.org/show_bug.cgi?id=569667 Pull More AMO Data]
* [https://bugzilla.mozilla.org/show_bug.cgi?id=563909 Accessibility]
|-
|}
 
 
=== Feature Description  ===
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.
 
= [[#Feature Release Readiness Assessment_Details|Feature Release Readiness Assessment]] =
 
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.
 
{| class="fullwidth-table"
|-
! Milestone
! Assessment
|-
| [[#Beta1]]
| Ready to Ship
|-
| [[#Beta2]]
| N/A
|-
| [[#Beta3]]
| N/A
|}
 
[[#Feature_Description|top]]
 
= [[#Feature_Documentation_Details|Feature Documentation]] =
 
{| class="fullwidth-table"
|-
! Item
! Description
! Status
|-
| [[#Project_Wiki]]
| Wiki Links to all feature related entries
|
|-
| [[#Developer_Links|#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.
|
|}
 
[[#Feature_Description|top]]
 
= [[#Feature_Bug_Management_Details|Feature Bug Management]] =
 
{| class="fullwidth-table"
|-
! Item
! Description
! Status
|-
| [[#Bug_Tracking]]
| Top level bugs tracking feature 
|
|-
| [[#Bug_Verification]]
| Feature bugs that need verification 
|
|-
| [[#Bug_Triage]]
| Links triage bug tasks 
|
|}
 
[[#Feature_Description|top]]
 
= [[#Feature_Test_Items_Details|Feature Test Items]] =
 
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'''
 
{| class="fullwidth-table"
|-
! Test Item
! Description
! Covered By
! Status
|-
| Item 1
| Item 1 Description
| Developer Tests
|
|-
| Item 2
| Item 2 Description
| Beta tester exposure
|
|-
| [[#Localization]]
| Feature localization
|
|
|-
| [[#Accessibility]] 
| Feature accessibility
|
|
|-
| [[#Plugins]]
| Plugins compatibility 
|
|
|-
| [[#Addons]]
| Addons compatibility 
|
|
|-
| [[#Topsites]]
| Top internet sites compatibilities 
|
|
|}
[[#Feature_Description|top]]
 
 
= [[#Feature_Tests_Details|Feature Tests]] =
== [[#Automated_Tests_Details|Automated Tests]] ==
{| class="fullwidth-table"
|-
! Item
! Description
! Status
|-
| [[#Developer_Tests]]
| Links to automated developer tests
|
|-
| [[#Mozmill_Tests]]
| Links to automated mozmill feature test cases 
|
|}
 
== [[#Manual_Tests_Details|Manual Tests]] ==
{| class="fullwidth-table"
|-
! Item
! Description
! Status
|-
| [[#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
|
|}
 
[[#Feature_Description|top]]
 
= [[#Community_Test_Events_Details|Community Test Events]] =
{| class="fullwidth-table"
|-
! Item
! Description
! Status
|-
| [[#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
|
|}
 
[[#Feature_Description|top]]
 
= [[#Feature_Documentation|Feature Documentation Details]] =
== Project Wiki ==
* [https://wiki.mozilla.org/Firefox/Projects/Extension_Manager_Redesign Add-ons Manager Redesign]
* [https://wiki.mozilla.org/Firefox/Projects/Extension_Manager_API Extension Manager API rewrite]
* [http://docs.google.com/Doc?docid=0Acwo2Bn17-PrZGZudHRobnJfNDJ0cTV0NjRnZA&hl=en Discovery Pane]
* [https://wiki.mozilla.org/AMO:Projects/ACR Add-ons Compatibility Reporter]
* [https://wiki.mozilla.org/Firefox/Projects/Pull_More_AMO_Data_into_Addons_Manager Pull more AMO Data into the Add-ons Manager]
 
[[#Feature_Documentation|top]]
 
== Developer Links ==
* [10/05/27] [http://www.oxymoronical.com/blog/2010/05/Support-for-dropping-XPI-files-into-the-extension-install-locations Support for dropping XPI files into the extension install locations might be going away]
* [10/05/10] [http://theunfocused.net/2010/05/10/status-update-extension-manager-ui-app-tabs/ Frontend Updates]
* [10/04/29] [http://www.oxymoronical.com/blog/2010/04/The-new-add-ons-manager-is-here The new Add-ons Manager is here]
* [10/04/27] [http://theunfocused.net/2010/04/27/status-update-extension-manager-ui/ Frontend Updates]
* [10/04/13] [http://theunfocused.net/2010/04/13/status-update-extension-manager-ui-tab-matches/ Frontend Updates]
* [10/04/01] [http://jboriss.wordpress.com/2010/04/01/add-ons-manager-redesign-update/ Add-ons Manager Redesign Update]
* [10/03/24] [http://blog.fligtar.com/2010/03/24/a-new-front-door/ A New Front Door]
* [10/03/22] [http://theunfocused.net/2010/03/23/status-update-extension-manager-ui-redesign/ Frontend Updates]
* [10/03/19] [http://www.oxymoronical.com/blog/2010/03/How-were-breaking-some-extensions-in-the-near-future How we’re breaking some extensions in the near future]
* [10/03/14] [http://www.oxymoronical.com/blog/2010/03/Look-Ma-no-restarts Look Ma, no restarts!]
* [10/03/12] [http://www.oxymoronical.com/blog/2010/03/Simplifying Simplifying]
* [10/01/07] [http://www.oxymoronical.com/blog/2010/01/Do-we-need-extension-dependencies Do we need extension dependencies?]
* [09/12/03] [http://jboriss.wordpress.com/2009/12/03/relocating-firefox%E2%80%99s-add-ons-manager/ Relocating Firefox’s Add-ons Manager]
* [09/11/23] [http://jboriss.wordpress.com/2009/11/23/redesigning-firefoxs-addons-manager/ Redesigning Firefox’s Addons Manager]
 
[[#Feature_Documentation|top]]
 
== Other Docs ==
* [https://wiki.mozilla.org/AMO:AOM_Meeting AMO Meeting notes]
 
[[#Feature_Documentation|top]]
 
== 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?
 
[[#Feature_Documentation|top]]
 
= [[#Feature_Release_Readiness_Assessment|Feature Release Readiness Assessment Details]] =
 
== Beta1 ==
 
== Beta2 ==
 
== Beta3 ==
 
= [[#Feature_Bug_Management|Feature Bug Management Details]] =
== Bug Tracking ==
* Top level bugs tracking feature. Include any relevant bug queries that are helpful for tracking feature status.


== Team Members==
{| class="fullwidth-table"
{| class="fullwidth-table"
| style="background: #EFEFEF; width: 33%" | '''Team'''
|-
| style="background: #EFEFEF; width: 33%" | '''Status'''
! Query Name
|- valign="top"
! Description
| QA
|-
* Henrik Skupin (QA lead)
| Add-ons Manager (interface and backend):
* Raymond Etornam (Discovery Pane)
* Blocker: [http://tinyurl.com/24858er alpha5]
* Marco Zehe (Accessibility)
* Blocker: [http://tinyurl.com/2fjgzl9 beta1]
  | Current status:
* Blocker: [http://tinyurl.com/2fn33bb beta2]
* Testplan creation / Testing
* Blocker: [http://tinyurl.com/2b45cr7 final]
* Testplan creation
* Triage: [http://tinyurl.com/235oa2m uiwanted]
* Testing
* Triage: [http://tinyurl.com/2blqg7h all]
* Waiting
* Triage: [http://tinyurl.com/242j28v open]
|}
* Triage: [http://tinyurl.com/2496tsm unconfirmed]
* Tests: [http://tinyurl.com/2fgn8y3 flags missing]
* Tests: [http://tinyurl.com/28wrv8o in-testsuite?]
* Tests: [http://tinyurl.com/2843lm8 in-testsuite+]
* Tests: [http://tinyurl.com/27acxzj in-litmus?]
* Tests: [http://tinyurl.com/29jh5b5 in-litmus+]
|
|-
| Discovery Pane:
|
|-
| Add-ons Compatibility Reporter:
* Triage: [http://tinyurl.com/2ftkw4u all]
* Triage: [http://tinyurl.com/28bvk7l open]
* Triage: [http://tinyurl.com/2ap8hgm unconfirmed]
|
|-
| Pull More AMO Data into the Add-ons Manager:
|
|-
| Top Issues:
* {{bug|565930}} - ACR inclusion?
* {{bug|520124}} - Personas on top of custom themes
* {{bug|553455}} - Missing notification box
* {{bug|553493}} - UI for restartless add-ons
* {{bug|562622}} - Update design mockups
* {{bug|562902}} - Detail pane mockups
| Open bugs which blocks testing of a specific area.
|}
 
[[#Feature_Bug_Management|top]]
 
== Bug Verification ==
* [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&field0-0-0=blocked&bug_status=RESOLVED&type0-0-1=substring&value0-0-1=AddonsRewrite&type0-0-0=anywordssubstr&field0-0-1=status_whiteboard&value0-0-0=461973%2C550048%2C553169%2C558289%2C558289 Fixed bugs] (need verification).
* [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&field0-0-0=blocked&bug_status=VERIFIED&type0-0-1=substring&value0-0-1=AddonsRewrite&type0-0-0=anywordssubstr&field0-0-1=status_whiteboard&value0-0-0=461973%2C550048%2C553169%2C558289%2C558289 Verified bugs]
 
[[#Feature_Bug_Management|top]]
 
== Bug Triage ==
* Bug triage information
 
[[#Feature_Bug_Management|top]]
 
= [[#Feature_Test_Items|Feature Test Items Details]] =
 
== Localization ==
 
* Details of feature localization test requirements
 
[[#Feature_Test_Items|top]]
 
== Accessibility == 
* 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.).
 
[[#Feature_Test_Items|top]]
 
== Plugins ==
* Details of plugins compatibility test requirements
 
[[#Feature_Test_Items|top]]
 
== Addons ==
* Details of addons compatibility  
 
[[#Feature_Test_Items|top]]
 
== Topsites ==
* Details of top internet sites test requirements
 
[[#Feature_Test_Items|top]]
 
= [[#Feature_Tests|Feature Tests Details]] =
To test all of the new features which will come with Firefox 4 we have setup a test plan which can be found on [http://spreadsheets.google.com/ccc?key=txGbPoaoGuoJW2P9cBdWL8g Google Spreadsheets].
 
== [[#Automated_Tests|Automated Tests Details]] ==
 
=== Developer Tests ===
* Links to automated developer tests
 
[[#Feature_Tests|top]]
 
=== Mozmill 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.


= Bug Queries =
List of Mozmill Tests:
<small>'''Tracking Bugs:''' [https://bugzilla.mozilla.org/show_bug.cgi?id=550048 Redesign Addons Manager UI] | [https://bugzilla.mozilla.org/show_bug.cgi?id=461973 Extension Manager API Rewrite]
* Links to automated mozmill feature test cases 
[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=runnamed&namedcmd=DiscoveryPane Discovery Pane] | [https://bugzilla.mozilla.org/show_bug.cgi?id=563909 Accessibility]</small>


<small>'''Triage:''' [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&field0-0-0=blocked&type0-0-0=anywordssubstr&value0-0-0=461973%2C550048%2C553169%2C558289%2C558289&type0-0-1=substring&value0-0-1=AddonsRewrite&field0-0-1=status_whiteboard all] | [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&field0-0-0=blocked&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&type0-0-1=substring&value0-0-1=AddonsRewrite&type0-0-0=anywordssubstr&field0-0-1=status_whiteboard&value0-0-0=461973%2C550048%2C553169%2C558289%2C558289 open] | [https://bugzilla.mozilla.org/buglist.cgi?keywords=uiwanted&query_format=advanced&keywords_type=allwords&field0-0-0=blocked&type0-0-0=anywordssubstr&value0-0-0=461973%2C550048%2C553169%2C558289&type0-0-1=substring&value0-0-1=AddonsRewrite&field0-0-1=status_whiteboard uiwanted] | [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&field0-0-0=blocked&bug_status=UNCONFIRMED&type0-0-0=anywordssubstr&value0-0-0=461973%2C550048%2C553169%2C558289&type0-0-1=substring&value0-0-1=AddonsRewrite&field0-0-1=status_whiteboard unconfirmed] | [https://bugzilla.mozilla.org/buglist.cgi?type0-1-0=notsubstring&field0-1-0=status_whiteboard&field0-0-0=blocked&query_format=advanced&value0-1-0=fixed-in-addonsmgr&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&type0-0-0=anywordssubstr&value0-0-0=461973%2C550048%2C553169%2C558289&type0-0-1=substring&value0-0-1=AddonsRewrite&field0-0-1=status_whiteboard assigned] | [https://bugzilla.mozilla.org/buglist.cgi?type0-1-0=substring&query_format=advanced&value0-1-0=fixed-in-addonsmgr&field0-1-0=status_whiteboard&field0-0-0=blocked&bug_status=ASSIGNED&bug_status=RESOLVED&type0-0-0=anywordssubstr&value0-0-0=461973%2C550048%2C553169%2C558289&type0-0-1=substring&value0-0-1=AddonsRewrite&field0-0-1=status_whiteboard fixed] | [https://bugzilla.mozilla.org/buglist.cgi?type0-1-0=substring&query_format=advanced&value0-1-0=fixed-in-addonsmgr&field0-1-0=status_whiteboard&field0-0-0=blocked&bug_status=VERIFIED&type0-0-0=anywordssubstr&value0-0-0=461973%2C550048%2C553169%2C558289&type0-0-1=substring&value0-0-1=AddonsRewrite&field0-0-1=status_whiteboard verified] | [https://bugzilla.mozilla.org/buglist.cgi?priority=P1&type0-1-0=anywordssubstr&query_format=advanced&value0-1-0=needs-review&field0-1-0=status_whiteboard&field0-0-0=blocked&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=CLOSED&type0-0-0=anywordssubstr&value0-0-0=461973%2C550048%2C553169%2C558289%2C558289&type0-0-1=substring&value0-0-1=AddonsRewrite&field0-0-1=status_whiteboard P1 blocker]</small>
[[#Feature_Tests|top]]


<small>'''Blockers:''' [https://bugzilla.mozilla.org/buglist.cgi?type0-1-0=substring&field0-1-0=cf_blocking_193&field0-0-0=blocked&type0-0-1=substring&field0-0-1=status_whiteboard&query_format=advanced&value0-1-0=alpha5%2B&value0-0-1=AddonsRewrite&type0-0-0=anywordssubstr&value0-0-0=461973%2C550048%2C553169%2C558289%2C558289 alpha5] | [https://bugzilla.mozilla.org/buglist.cgi?type0-1-0=substring&field0-1-0=cf_blocking_193&field0-0-0=blocked&type0-0-1=substring&field0-0-1=status_whiteboard&query_format=advanced&value0-1-0=beta1%2B&value0-0-1=AddonsRewrite&type0-0-0=anywordssubstr&value0-0-0=461973%2C550048%2C553169%2C558289%2C558289 beta1] | [https://bugzilla.mozilla.org/buglist.cgi?type0-1-0=substring&field0-1-0=cf_blocking_193&field0-0-0=blocked&type0-0-1=substring&field0-0-1=status_whiteboard&query_format=advanced&value0-1-0=final%2B&value0-0-1=AddonsRewrite&type0-0-0=anywordssubstr&value0-0-0=461973%2C550048%2C553169%2C558289%2C558289 final]
== [[#Manual_Tests|Manual Tests Details]] ==
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 [http://spreadsheets.google.com/ccc?key=0AlroormSQgiRdDZhVEJqcF9ITFNLLW5zMURzMUROQXc&hl=en#gid=0 Google Spreadsheet].


<small>'''Tests:''' [https://bugzilla.mozilla.org/buglist.cgi?type0-1-0=notsubstring&field0-1-0=flagtypes.name&field0-0-0=blocked&type0-0-1=substring&type0-1-1=notsubstring&field0-0-1=status_whiteboard&resolution=FIXED&resolution=---&query_format=advanced&value0-1-0=in-testsuite&value0-1-1=in-litmus&field0-1-1=flagtypes.name&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&value0-0-1=AddonsRewrite&type0-0-0=anywordssubstr&value0-0-0=461973%2C550048%2C553169%2C558289%20in-testsuite%3F missing flags] | [https://bugzilla.mozilla.org/buglist.cgi?type0-1-0=substring&field0-1-0=flagtypes.name&field0-0-0=blocked&type0-0-1=substring&field0-0-1=status_whiteboard&resolution=FIXED&resolution=---&query_format=advanced&value0-1-0=in-testsuite%3F&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&value0-0-1=AddonsRewrite&type0-0-0=anywordssubstr&value0-0-0=461973%2C550048%2C553169%2C558289%20in-testsuite%3F in-testsuite?] | [https://bugzilla.mozilla.org/buglist.cgi?type0-1-0=substring&field0-1-0=flagtypes.name&field0-0-0=blocked&type0-0-1=substring&field0-0-1=status_whiteboard&resolution=FIXED&resolution=---&query_format=advanced&value0-1-0=in-testsuite%2B&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&value0-0-1=AddonsRewrite&type0-0-0=anywordssubstr&value0-0-0=461973%2C550048%2C553169%2C558289%20in-testsuite%3F in-testsuite+] | [https://bugzilla.mozilla.org/buglist.cgi?type0-1-0=substring&field0-1-0=flagtypes.name&field0-0-0=blocked&type0-0-1=substring&field0-0-1=status_whiteboard&resolution=FIXED&resolution=---&query_format=advanced&value0-1-0=in-litmus%3F&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&value0-0-1=AddonsRewrite&type0-0-0=anywordssubstr&value0-0-0=461973%2C550048%2C553169%2C558289%20in-testsuite%3F in-litmus?] | [https://bugzilla.mozilla.org/buglist.cgi?type0-1-0=substring&field0-1-0=flagtypes.name&field0-0-0=blocked&type0-0-1=substring&field0-0-1=status_whiteboard&resolution=FIXED&resolution=---&query_format=advanced&value0-1-0=in-litmus%2B&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&value0-0-1=AddonsRewrite&type0-0-0=anywordssubstr&value0-0-0=461973%2C550048%2C553169%2C558289%20in-testsuite%3F in-litmus+]</small>
=== Smoke_Tests ===
* links to litmus smoke tests or description


= Top Issues =
[[#Feature_Tests|top]]
* {{bug|553455}}: No notification of addons being installed
* {{bug|553493}}: Make sure UI works as expected for installing restart-less addons
* {{bug|562622}}: Implementation of the automatic vs. manual update design mockups
* {{bug|562902}}: Implementation of the Detail View design mockups
* {{bug|562760}}: Language packs cannot be installed
* {{bug|565610}}: Can not overlay about: urls
* {{bug|520124}}: Personas on top of other custom themes


= Things We Will Work On =
=== Regression_Tests ===
The complete test plan can be found on [http://spreadsheets.google.com/ccc?key=txGbPoaoGuoJW2P9cBdWL8g Google Spreadsheets].
* links to litmus BFT and/or regression tests description


; Additional Work
[[#Feature_Tests|top]]
* Creating and Updating existent Litmus tests ([http://spreadsheets.google.com/ccc?key=0AspwyJKepmCudDV1WF9mM25IVnh6M1NyaHU2NU8zMUE&hl=en&pli=1#gid=0 coverage spreadsheet])
* Revising Mozmill tests for Add-ons Manager


= Things We Don't Test =
=== Functional_Tests ===
We do not test any area which is already covered by automated tests.
* links to litmus FFT and/or complete functional tests description


= Reference =
[[#Feature_Tests|top]]
* Firefox project pages
** [https://wiki.mozilla.org/Firefox/Projects/Extension_Manager_API Extension Manager API rewrite]
** [https://wiki.mozilla.org/Firefox/Projects/Extension_Manager_Redesign Extension Manager UI redesign]
*** [https://wiki.mozilla.org/Firefox/Projects/Extension_Manager_Redesign/design Current Design]
** [http://docs.google.com/Doc?docid=0Acwo2Bn17-PrZGZudHRobnJfNDJ0cTV0NjRnZA&hl=en Discovery Pane]


* Test days:
= [[#Community_Test_Events|Community Test Events Details]] =
** [[/QA/Firefox_3.next/Test_Plan:AddonsManagerRedesign/Testday-10-04-30|Testday on April 30th]]
== Testdays ==
* [10/04/30] [http://quality.mozilla.org/qmo-news/2010/results-of-add-ons-manager-testday/ Results] of the [http://www.hskupin.info/2010/04/24/testday-exploratory-testing-the-new-add-ons-manager/ first Add-ons Manager testday]
* [10/06/11] [http://www.hskupin.info/2010/06/09/second-add-ons-manager-redesign-testday-this-friday/ Second Add-ons Manager testday]


* Blog posts:
== Bugdays ==
** 10/05/27 - Dave: [http://www.oxymoronical.com/blog/2010/05/Support-for-dropping-XPI-files-into-the-extension-install-locations Support for dropping XPI files into the extension install locations might be going away]
None
** 10/05/10 - Blair: [http://theunfocused.net/2010/05/10/status-update-extension-manager-ui-app-tabs/ Frontend Updates]
** 10/04/29 - Dave: [http://www.oxymoronical.com/blog/2010/04/The-new-add-ons-manager-is-here The new Add-ons Manager is here]
** 10/04/27 - Blair: [http://theunfocused.net/2010/04/27/status-update-extension-manager-ui/ Frontend Updates]
** 10/04/13 - Blair: [http://theunfocused.net/2010/04/13/status-update-extension-manager-ui-tab-matches/ Frontend Updates]
** 10/04/01 - Boriss: [http://jboriss.wordpress.com/2010/04/01/add-ons-manager-redesign-update/ Add-ons Manager Redesign Update]
** 10/03/24 - Justin: [http://blog.fligtar.com/2010/03/24/a-new-front-door/ A New Front Door]
** 10/03/22 - Blair: [http://theunfocused.net/2010/03/23/status-update-extension-manager-ui-redesign/ Frontend Updates]
** 10/03/19 - Dave: [http://www.oxymoronical.com/blog/2010/03/How-were-breaking-some-extensions-in-the-near-future How we’re breaking some extensions in the near future]
** 10/03/14 - Dave: [http://www.oxymoronical.com/blog/2010/03/Look-Ma-no-restarts Look Ma, no restarts!]
** 10/03/12 - Dave: [http://www.oxymoronical.com/blog/2010/03/Simplifying Simplifying]
** 10/01/07 - Dave: [http://www.oxymoronical.com/blog/2010/01/Do-we-need-extension-dependencies Do we need extension dependencies?]
** 09/12/03 - Boriss: [http://jboriss.wordpress.com/2009/12/03/relocating-firefox%E2%80%99s-add-ons-manager/ Relocating Firefox’s Add-ons Manager]
** 09/11/23 - Boriss: [http://jboriss.wordpress.com/2009/11/23/redesigning-firefoxs-addons-manager/ Redesigning Firefox’s Addons Manager]


= Discussion / Meetings =
== Meetups ==
* [https://wiki.mozilla.org/AMO:AOM_Meeting Meeting notes]
None
* [https://wiki.mozilla.org/QA/Firefox_3.next/Test_Plan:AddonsManagerRedesign/Meeting:20100304 20100304 - AMO meeting]
* [https://wiki.mozilla.org/QA/Firefox_3.next/Test_Plan:AddonsManagerRedesign/Meeting:20100303 20100303 - First come together]

Latest revision as of 21:47, 30 June 2010

« Firefox 4 TestPlan

Add-ons Manager Redesign

Area Details
Development Status: In progress (10/06/09)
Feature Testing: In progress (10/06/09)
Team: By group:
  • Jennifer Boriss (UX)
  • Dave Townsend, Blair McBride, Robert Strong, Ben Parr, Benedict Hsieh (Add-ons Manager)
  • Justin Scott, Jeff Balogh (Discovery Pane)
  • Brian King, David McNamara (Add-on Compatibility Reporter)
  • Henrik Skupin, Marco Zehe, Raymond Etornam (QA)
Tracking Bugs By sub-project:


Feature Description

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.

Feature Release Readiness Assessment

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.

Milestone Assessment
#Beta1 Ready to Ship
#Beta2 N/A
#Beta3 N/A

top

Feature Documentation

Item Description Status
#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.

top

Feature Bug Management

Item Description Status
#Bug_Tracking Top level bugs tracking feature
#Bug_Verification Feature bugs that need verification
#Bug_Triage Links triage bug tasks

top

Feature Test Items

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
#Localization Feature localization
#Accessibility Feature accessibility
#Plugins Plugins compatibility
#Addons Addons compatibility
#Topsites Top internet sites compatibilities

top


Feature Tests

Automated Tests

Item Description Status
#Developer_Tests Links to automated developer tests
#Mozmill_Tests Links to automated mozmill feature test cases

Manual Tests

Item Description Status
#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

top

Community Test Events

Item Description Status
#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

top

Feature Documentation Details

Project Wiki

top

Developer Links

top

Other Docs

top

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

Feature Release Readiness Assessment Details

Beta1

Beta2

Beta3

Feature Bug Management Details

Bug Tracking

  • Top level bugs tracking feature. Include any relevant bug queries that are helpful for tracking feature status.
Query Name Description
Add-ons Manager (interface and backend):
Discovery Pane:
Add-ons Compatibility Reporter:
Pull More AMO Data into the Add-ons Manager:
Top Issues: Open bugs which blocks testing of a specific area.

top

Bug Verification

top

Bug Triage

  • Bug triage information

top

Feature Test Items Details

Localization

  • Details of feature localization test requirements

top

Accessibility

  • 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.).

top

Plugins

  • Details of plugins compatibility test requirements

top

Addons

  • Details of addons compatibility

top

Topsites

  • Details of top internet sites test requirements

top

Feature Tests Details

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.

Automated Tests Details

Developer Tests

  • Links to automated developer tests

top

Mozmill 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

top

Manual Tests Details

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.

Smoke_Tests

  • links to litmus smoke tests or description

top

Regression_Tests

  • links to litmus BFT and/or regression tests description

top

Functional_Tests

  • links to litmus FFT and/or complete functional tests description

top

Community Test Events Details

Testdays

Bugdays

None

Meetups

None

Retrieved from "https://wiki.allizom.org/index.php?title=QA/Firefox_3.next/Test_Plan:AddonsManagerRedesign&oldid=235545"