TestEngineering/UI/AMO/5.0.7 Test Plan

AMO 5.0.7 Test Plan
Release description

• Implement Tagging in AMO.Major obejctives include:
  • Make it easier for users to pivot through add-ons based on a variety of descriptive tags
  • Give users a place to go next after they install an add-on
  • Allow both users and developers to tag add-ons
• Implement Contributions in Add-on details page.This feature affects the layout of the add-ons details page.Major objectives include:
  • Help developers receive financial contributions for their work
  • Raise awareness of Mozilla and its role in keeping the internet free
  • Communicate to users the value of contributing and give developers an avenue for communicating their roadmap and how contributions will be used
• Bug fixes for 5.0.7

Staging server:
AMO Staging

Requirements/Specifications

• Tagging specs
• Contribution specs

Acceptance doc:

• ?

Planned Release date:

• 06/30/2009(tentative)

QA Resources:

• Stephen Donner (irc:stephend)
• Krupa Raj (irc:krupa)
• Raymond Etornam (irc:retornam)

Major areas(positive testcases)which need to be validated:

• Tagging:
  • Verification of Tag format
  • Addition of single/multiple tag(s)
  • Deletion of single/multiple tag(s)
  • Searching for tags
  • Format of Top Tag cloud/tag details page
  • Sorting of popular tags
  • Tag intersections
  • Related Tags
  • Tags/add-on upper limit for Developers/users
  • Duplicate Tags
  • Normalization [example:book marks=bookmarks]
  • Tag blacklist
  • Tag auto-complete
  • Developer vs User tags

• Contributions:
  • Layout of Add-ons details page
  • Updates to developer profiles
  • Updates to submit/edit add-on pages
  • Turning off contributions
  • Setting up contributions for diff add-ons
  • Options for providing contribution links
    • Free
    • Default "free flow" with contribution link alongside "Add to [application]" button
    • Interstitial profile/contribution page after clicking "Add to Firefox" with simultaneous downloading of xpi
    • Interstitial page with "donate" and "continue without contributing" buttons
  • Tracking revenue history
  • Paypal Integration
  • Making a contribution(this is a huge testcase by itself)
  • Requesting features
  • Landing page access only during install/upgrade
  • Contributions allowed for single-author add-ons only
  • Metrics collection(do we test this?)

What is out of scope:

• Unit Testing
• Performance testing (Load, Volume, Stress)
• White Box testing
• In-depth Security testing

Entry and Exit Criteria:

• Entry criteria:
  • The most up-to-date mocks/specs are made available to the QA team
  • The features are ready for QA

• Exit Criteria
  • No crashing bugs
  • All features under the scope of this release are functional.
  • All P1 and P2 bugs are either fixed or deferred.
  • All P1/P2 fixes are verified by QA and marked as such in Bugzilla.
  • QA has verified that the fixes have not caused major regression.

Test deliverables:

• Test Plan
• Bug reports
• Interim status updates

Assumptions and Risk Management:

• Assumptions:
  • There is no schedule slippage from development.
  • No feature creep.
  • Push to production does not coincide with other major releases(like SUMO).

• Risks and their management:
  • In case of any schedule slippage,AMO team will regroup and evaluate the planned release date.
  • If any QA resource is unavailable for testing for extended duration,planned release date will be re-evaluated.