Add-ons/QA/Testplan/Implement mozAddonManager features in the install buttons

From MozillaWiki
Jump to: navigation, search

Revision History

Date Version Author Description
31/08/2018 1.0 Alexandra Gal-Moga Created first draft

Overview

  • This feature brings more utilities to AMO add-on installation buttons, linking them to functions currently available in addons manager.
  • Specifically, AMO (frontend and disco pane) install buttons will receive the following functions:
    • show download progress
    • reflect installation state
    • support uninstallation

Goals

  • Make installation status on AMO more evident;
  • Managextensions directly from AMO, without having to necessarily open addons:manager in order to view the list of installed add-ons;
  • Users will immediately know if an add-on they visit on AMO is already installed (active or inactive) in their browser.

Entry Criteria

  • functional specifications are fully agreed
  • UX specification have been provided
  • The feature has landed in -dev

Current Status

  • The feature is under test in AMO -dev

Exit Criteria

  • All related bugs triaged
  • All blockers fixed
  • All resolved bugs verified by QA
  • Found-fixed bugs rate going down in time

Scope

what's in scope?

  • Installation is working foe all available add-on types:
    • extensions
    • lightweight themes
    • static themes
    • dictionaries and language packs
    • search tools
  • The new install features are supported on multiple platforms and Firefox versions
  • AMO frontend and addons:manager are fully integrated to render the correct installation status


what's out of scope?

  • Add-ons/Webextensions functionality

Risks

  • This feature has a medium risk level, on the reason that the new install functionalities needs to be fully operational on multiple platforms and Firefox versions

Ownership

Product Manager: Jorge Villalobos; irc nick :jorgev
QA Manager: Krupa Raj; irc nick :krupa
QA Lead: Victor Carciu; irc nick :victorc
Add-ons QA: Alexandra Moga; irc nick :LexaSV

Requirements for testing

Environments

  • Windows 10x64
  • Windows 7x64
  • Mac OS
  • Linux
  • Android

Servers

Channels

  • Nightly
  • Beta
  • Release
  • ESR

Non - Firefox Browsers

  • Safari
  • Chrome
  • Edge

Test Strategy

Test Execution Schedule

The following table identifies the anticipated testing period available for test execution.

Project phase Date
Start project 21.07.2017
QA - Test plan creation 31.08.2018
QA - Test scenarios preparation 31.08.2018
QA - Test cases execution 03.09.2018
Release Date TBA

Testing Tools

Process Tool
Test plan creation Mozilla wiki
Test case creation Google doc
Bugs management Github

References


Sign off

Criteria

Check list

  • All tests should be executed
  • All blockers must be fixed and verified or have an agreed-upon timeline for being fixed